Methods and apparatus for managing renewable energy services

ABSTRACT

Methods and apparatus for managing at least one renewable energy source for supply of power via an electric grid are disclosed. A method supplies power to mobile devices from the renewable energy source and balances power realized by the mobile devices with the supply of power from the renewable energy source by controlling the supply of power realized by the mobile devices. An apparatus includes a processor for monitoring power from the renewable energy source and sending signals to mobile devices connected to the electric grid to balance monitored power from the renewable energy source with power realized by the mobile devices. Another method identifies a fixed account associated with a grid connection point used by a plug-in electric vehicle for realizing power during a connection event; determines a quantity of energy realized during the event; and adjusts the account based on energy realized by the vehicle during the event.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional Appl. No.61/407,285 entitled “Method and Apparatus for Reconciliation of aCharging Event,” filed Oct. 27, 2010; U.S. Provisional Appl. No.61/407,293, entitled “Methods and Apparatus for Identifying a GridConnection Point Using a Tag,” filed Oct. 27, 2010; U.S. ProvisionalAppl. No. 61/419,594, entitled “Methods and Apparatus for ManagingRenewable Energy Services,” filed Dec. 3, 2010; U.S. Provisional Appl.No. 61/421,782, entitled “Methods And Apparatus for Managing EnergyServices From a Plurality of Devices,” filed Dec. 10, 2010; U.S.Provisional Appl. No. 61/421,793, entitled “Methods and Apparatus forManaging Energy Services for Fixed and Mobile Assets,” filed Dec. 10,2010; and U.S. Provisional Appl. No. 61/424,534, entitled “Methods andApparatus for Managing Energy Services for Fixed and Mobile Assets,”filed Dec. 17, 2010; which are incorporated by reference herein in theirentireties.

BACKGROUND OF THE DISCLOSURE

Field of the Disclosure

The field of the disclosure relates generally to energy services, and,more particularly, to renewable energy services for mobile devices.

Description of the Related Art

RFID tags and bar code tags are used in different applications toidentify products for sale. In such applications, the barcode tags orthe RFID tags are placed on sale products to identify the sale products,for example, to a point-of-sale system. Validation of the barcode tagsor RFID tags occur from a reader (e.g., a barcode reader or an RFIDreader) associated with the point-of-sale system to ensue properidentification of the sale product.

SUMMARY OF THE DISCLOSURE

The present disclosure is directed to exemplary methods, exemplaryapparatus and exemplary systems that include an identification unitassociated with an electrical outlet, and configured to present a uniqueidentification for the electrical outlet.

The present disclosure is directed to exemplary methods, exemplaryplug-in vehicles, exemplary charging stations and systems. One exemplarysystem includes a plug-in vehicle for connection to a charging stationhaving a station connector. The plug-in vehicle includes an electricstorage unit for storing electric power from (or via) the chargingstation, a plug-in vehicle connector configured to connect to thecharging station for transfer of the electric power to or from theelectric storage unit and an identification reader that is coupled tothe plug-in vehicle connector for reading a unique identity presented bythe charging station. The exemplary system also includes a chargingstation having an electrical power source for distributing electricpower to the plug-in vehicle, a power source connector configured toconnect to the plug-in vehicle connector for charging the plug-invehicle and an identification tag configured to present a uniqueidentification that is associated with the charging station to theplug-in vehicle.

The present disclosure is also directed to exemplary methods, apparatusand computer readable storage media. One exemplary method of identifyinga grid connection point for bill processing of a charging event includesestablishing an identity tag at the grid connection point that uniquelyidentifies the grid connection point, receiving, by a mobile chargingdevice, identity tag information to uniquely identify the gridconnection point, and monitoring, by the mobile charging device, chargeevent information indicating attributes of the charging event. Theexemplary method further includes associating, by the mobile chargingdevice, the charging event information with the identity taginformation, as associated information and sending, by the mobilecharging device, the associated information for reconciliation ofbilling accounts associated with the grid connection point and themobile charging device.

The present disclosure is also directed to exemplary methods, apparatusand non-transitory computer readable medium. One exemplary method thatmanages at least one renewable energy source for supply of power via anelectric grid includes: supplying power to mobile devices from therenewable energy source, via the electric grid; and balancing the powerrealized by the mobile devices with the supply of power from therenewable energy source by controlling the supply of power realized bythe mobile devices. One other exemplary method includes: (1) identifyinga fixed account that is associated with a grid connection point used byat least one plug-in electric vehicle for realizing power during aconnection event; (2) determining, by the at least one plug-in electricvehicle, a quantity of the energy realized during the connection event;and (3) adjusting the identified fixed account based on the energyrealized by the plug-in vehicle during the connection event. In yetanother exemplary method, at least one plug-in electric vehicle isregistered to a renewable energy account; and charged at grid connectionpoints associated with respectively different fixed accounts (as aplurality of charging events) such that the energy consumed by theplug-in electric vehicle during the charging events is aggregated andthe renewable energy account is billed, based on the aggregated energyconsumed.

A further exemplary method for managing energy service for a mobileasset connected to a grid connection point during a connection eventincludes: determining, by the mobile asset, a quantity of the energyservice realized during the connection event; identifying an accountassociated with the grid connection point; and adjusting the identifiedaccount based on the quantity determined by the mobile asset.

An additional exemplary method for managing energy service for an assetconnected to a grid connection point of an electric grid includes:receiving, by an energy service controller, an indicator indicating atleast one of: (1) an asset identifier that identifies the asset; or (2)an identifier that identifies the grid connection point connected to theasset; determining, by an energy service controller, a location of theasset on the electric grid based on the received indicator; determining,by the energy service controller, one or more operating conditions forrealizing the energy service based on at least the determined locationof the asset on the electric grid; and sending, by the energy servicecontroller to the asset, the determined one or more operating conditionsto realize the energy service. This method also includes identifying anaccount that is associated with the grid connection point based theindicator; and adjusting the identified account based on a quantity ofenergy services realized by the asset in accordance with the determinedone or more operating conditions.

Another exemplary method for managing energy service for a plurality ofassets of different types connected to grid connection points includesdetermining, by a respective asset of the plurality of assets, aquantity of the energy service realized by the respective asset during aconnection event, responsive to the respective asset being of a firsttype, detecting a grid connection point identifier that identifies agrid connection point associated with the respective asset of the firsttype used for the connection event; and sending, by the respectiveasset, connection event information, wherein the connection eventinformation includes at least one of: (1) the determined quantity of theenergy service and an asset identifier, responsive to the respectiveasset not being of the first type; or (2) the determined quantity of theenergy service and the detected grid connection point identifier,responsive to the respective asset being of the first type.

An exemplary billing apparatus for managing energy services realized byassets connected to grid connection points during connection events,includes an aggregation unit for: (1) receiving for each connectionevent an indicator indicating at least one of: (i) an asset identifierof an asset used during the connection event; or (ii) a grid connectionpoint identifier of the grid connection point connected to the assetused during the connection event; (2) identifying, for each connectionevent, an account that is associated with the grid connection pointbased the indicator; and (3) aggregating the connection eventinformation in accordance with the identified accounts; and a billingengine for adjusting the identified accounts based on the aggregatedconnection event information associated with the identified accounts.

A further exemplary method of managing energy service for a first typeof asset connected to grid connection points includes: reporting, by arespective asset of the first type, an identifier associated with a gridconnection point that establishes a location of the respective asset ofthe first type at the grid connection point on the electric grid;receiving, by the respective asset of the first type, one or moreoperating conditions for realizing the energy service, the receivedoperating conditions being based on the established location of therespective asset of the first type on the electric grid; and operatingthe respective asset of the first type in accordance with the receivedone or more operating conditions to realize the energy service.

A further exemplary method of managing energy service for a mobile assetconnected to a grid connection point of an electric grid includes:receiving, by an energy service controller, an identifier associatedwith the grid connection point connected to the mobile asset; anddetermining, by the energy service controller, a location of the mobileasset on the electric grid based on the received identifier. The methodalso includes: determining, by the energy service controller, one ormore operating conditions for realizing the energy service in accordancewith at least operating constraints associated with the determinedlocation of the mobile asset on the electric grid; and sending, by theenergy service controller to the mobile asset, the determined one ormore operating conditions for realizing the energy service.

Another exemplary method of managing energy service for an assetconnected to a grid connection point of an electric grid includes:receiving, by an energy service controller from the asset, an indicator;referencing, by the energy service controller, the indicator todetermine a vicinity of the asset on the electric grid; and generating,by the energy service controller, a control signal including controlinformation for realizing the energy service. The control signalinformation is based on operating constraint of the electric grid in avicinity of the asset and operating constraint indicated by the receivedindicator. This exemplary method also includes sending, by the energyservice controller to the asset, the control signal.

An additional exemplary method of managing energy service of a pluralityof assets of different types connected to grid connection pointsincludes: reporting, by a respective asset, connection informationincluding an asset identifier, responsive to the respective asset beingconnected to a respective grid connection point; receiving, by therespective asset, one or more operating conditions for realizing theenergy service. The received operating conditions are based on apredetermined location of the respective asset on the electric grid. Themethod also includes operating the respective asset in accordance withthe received one or more operating conditions to realize the energyservice.

A yet further exemplary method of managing an electric grid in which aplurality of mobile devices have an energy storage unit and areconnected to respective grid connection points to realize energyservices includes: reporting, by each respective mobile device, aconnection of the respective mobile device to a grid connection pointand constraints of the respective mobile device for realizing the energyservices; receiving authorization, by the respective mobile device, forthe energy services to be realized based on at least the reportedconstraints from the respective mobile device; and realizing, by therespective mobile device, the authorized energy services.

An exemplary mobile asset for realizing energy service includes: acommunication module for reporting an identifier associated with thegrid connection point that establishes a location of the mobile asset atthe grid connection point on the electric grid, and for receiving one ormore operating conditions for realizing the energy service, the receivedoperating conditions being based on the established location of themobile asset on the electric grid; and a processor for operating themobile asset in accordance with the received one or more operatingconditions to realize the energy service.

An exemplary energy service controller for managing energy servicerealized by a mobile asset connected to a grid connection point of anelectric grid includes: a communication unit for receiving from themobile asset an identifier associated with the grid connection pointconnected to the mobile asset; and a processor for determining alocation of the mobile asset on the electric grid based on theidentifier received by the communication unit, and for determining oneor more operating conditions for realizing the energy service inaccordance with at least operating constraints associated with thedetermined location of the mobile asset on the electric grid such thatthe communication unit sends to the mobile asset the determined one ormore operating conditions for realizing the energy service.

Methods and exemplary adapters for realizing energy services by a devicevia a grid connection point are disclosed. One exemplary adapterincludes a detection unit for measuring a quantity of energy servicesrealized by the mobile device; an identification unit for detecting theidentifier of the grid connection point electrically connected to thedevice; and a communication unit, coupled to the first and seconddetectors, to report connection event information including at least:(1) the quantity of the energy service realized by the device; (2) anidentifier associated with the adapter; and (3) the identifier of thegrid connection point.

Further features and advantages of the present invention, as well as thestructure and operation of various embodiments thereof, are described indetail below with reference to the accompanying drawings. It is notedthat the invention is not limited to the specific embodiments describedherein. Such embodiments are presented herein for illustrative purposesonly. Additional embodiments will be apparent to persons skilled in therelevant art(s) based on the teachings contained herein.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawings, which are incorporated herein and form partof the specification, illustrate the present invention and, togetherwith the description, further serve to explain the principles of theinvention and to enable a person skilled in the relevant art(s) to makeand use the invention. The exemplary embodiments are best understoodfrom the following detailed description when read in conjunction withthe accompanying drawings. It is emphasized that, according to commonpractice, the various features of the drawings are not to scale. On thecontrary, the dimensions of the various features are arbitrarilyexpanded or reduced for clarity. Included in the drawings are thefollowing figures:

FIG. 1 is a schematic diagram illustrating a system for identifying agrid connection point (GCP) to a mobile device in accordance with anexemplary embodiment;

FIG. 2A is a schematic diagram illustrating a system for identifying aGCP to a mobile device in accordance with another exemplary embodiment;

FIG. 2B is a schematic diagram illustrating a system for identifying aGCP to a mobile device in accordance with a further exemplaryembodiment;

FIG. 3 is a block diagram illustrating a system for managing billingadjustments in accordance with exemplary embodiment;

FIG. 4A is a top view illustrating an electrical outlet in accordancewith an exemplary embodiment;

FIG. 4B is a cross sectional view illustrating the electrical outlet ofFIG. 4A taken along a line A-A;

FIG. 4C is a top view illustrating an electrical outlet in accordancewith another exemplary embodiment;

FIG. 4D is a cross sectional view illustrating the electrical outlet ofFIG. 4C taken along a line B-B;

FIG. 4E is a top view illustrating an electrical outlet in accordancewith a further exemplary embodiment;

FIG. 4F is a cross sectional view illustrating the electrical outlet ofFIG. 4E taken along a line C-C;

FIG. 5 is a flowchart illustrating a method of associating chargingevent information with information of an identity tag in accordance withexemplary embodiments;

FIG. 6 is a flowchart illustrating a method of managing a charging eventin accordance with exemplary embodiments;

FIG. 7 is a flowchart illustrating a method of reconciling billingassociated with a charging event in accordance with exemplaryembodiments.

FIG. 8 is a block diagram illustrating a system for managing energyservices in accordance with exemplary embodiments;

FIG. 9 is a flowchart illustrating a method of managing at least onerenewable energy source in accordance with exemplary embodiments;

FIG. 10 is a flowchart illustrating a method of managing renewableenergy services in accordance with exemplary embodiments;

FIG. 11 is a flowchart illustrating a method of managing renewableenergy services in accordance with other exemplary embodiments;

FIG. 12 is a flowchart illustrating a method of managing energy servicesin accordance with exemplary embodiments;

FIG. 13 is a flowchart illustrating a method of managing energy servicesin accordance with further exemplary embodiments;

FIG. 14 is a flowchart illustrating a method of managing energy servicesin accordance with other exemplary embodiments;

FIG. 15 is a flowchart illustrating a method of managing energy servicesin accordance with additional exemplary embodiments;

FIG. 16 is a flowchart illustrating a method of managing energy servicesin accordance with yet further exemplary embodiments;

FIG. 17 is a flowchart illustrating a method of managing renewableenergy services in accordance with yet other exemplary embodiments;

FIG. 18 is a flowchart illustrating a method of managing energy servicesin accordance with yet additional exemplary embodiments;

FIG. 19 is a flowchart illustrating a method of managing an electricgrid in accordance with other exemplary embodiments;

FIG. 20 is a block diagram illustrating a system using the exemplaryadapter coupled to an electric device for realizing energy services inaccordance with exemplary embodiments;

FIG. 21 is a schematic diagram illustrating an exemplary adapter coupledto an electric device for realizing energy services in accordance withother exemplary embodiments;

FIG. 22 is a plan view illustrating the other exemplary adapter of FIG.20;

FIG. 23 is a flowchart illustrating a method of managing energy servicesusing an adapter in accordance with exemplary embodiments;

FIG. 24 is a flowchart illustrating a method of managing energy servicesusing an adapter in accordance with other exemplary embodiments; and

FIG. 25 is a flowchart illustrating a method of managing energy servicesusing an adapter in accordance with further exemplary embodiments.

FIG. 26 is a diagram of an example computer system in which embodimentscan be implemented.

The features and advantages of the present invention will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference charactersidentify corresponding elements throughout. In the drawings, likereference numbers generally indicate identical, functionally similar,and/or structurally similar elements. Generally, the drawing in which anelement first appears is indicated by the leftmost digit(s) in thecorresponding reference number.

DETAILED DESCRIPTION

Generally, validation of a sale occurs in a device (e.g., thepoint-of-sale system) operated by a merchant of the product for sale toensure a proper sale of the product. For example, many retail stores usebar code systems to identify a product for sale to a point-of-salesystem. The point-of-sale system may determine the sale price and maydebit a credit account associated with the customer buying the product,thereby, validating the product's cost and the proper billing of theproduct.

In various exemplary embodiments, a grid connection point (or gridcharging point) (GCP) may be identified to a mobile device such as aplug-in vehicle such that the plug-in vehicle manages the determinationof the power stored and initiates bill reconciliation for a chargingevent for the mobile device. By identifying the GCP and charging eventinformation, energy costs associated with charging the mobile device atmany different GCPs may be aggregated to a billing account. Billing tothe aggregated billing account may be at a fixed monthly rate or basedon the actual energy consumed during charging. The account associatedwith each GCP may be adjusted (e.g., reduced) based on the energyconsummated by the mobile device during specified events.

Although the mobile device is illustrated as charging from the GCP, oneof skill in the art understands that the mobile device (e.g., plug-invehicles (PEVs) including hybrid type vehicles) may supply power to theGCP and may be credited for the power and the billing of the customeraccount associated with the GCP may be adjusted (e.g., increased) basedon the energy supplied by the mobile device during the specified event.

In certain exemplary embodiments, an electric utility may provide thereconciliation services to enable the reconciliation of energy costsassociated with the specified events to the aggregated billing accountand corresponding adjustment of energy costs for billing accountsassociated with each of the GCPs used to charge or discharge the mobiledevice.

FIG. 1 is a schematic diagram illustrating a system 100 for identifyinga GCP 105 to a mobile device (MD) 120 in accordance with an exemplaryembodiment.

Referring to FIG. 1, system 100 may include the GCP 105, the MD 120(e.g., PEV or other mobile electrical devices having an electric storagecapability including, but not limited to, a battery driven power tool, aPersonal Digital Assistant (PDA), a tablet computing device, an iPhone™,an iPod™, an iPad™, a device operating the Android operating system (OS)from Google Inc., a device running the Microsoft Windows® Mobile OS, adevice running the Microsoft Windows® Phone OS, a device running theSymbian OS, a device running the webOS from Hewlett Packard, Inc., amobile phone, a BlackBerry® device, a smartphone, a hand held computer,a netbook computer, a palmtop computer, a laptop computer, anultra-mobile PC, a portable gaming system, or another similar type ofmobile device having an electric storage capability), a communicationnetwork 130, a reconciler 140 and an electric grid 150. The GCP 105 mayinclude a charging station 110, a grid connector 115 and an RFID tag119. The reconciler 140 may include a memory 146, a transceiver 147 anda controller 148.

MD 120 may include a mobile connector 121, an Energy Storage Device(ESD) 122, a Charge Management System (CMS) 123, and a meter device 124.

In certain exemplary embodiments, functions of the CMS 123 may beperformed by an existing controller of the MD 120. For example, in a PEVthe functions of the CMS 123 may be performed by a vehicle managementsystem (not shown).

The mobile connector 121 may be, for example, a J772 connector for PEVsor any other connector capable of charging the MD 120. The mobileconnector 121 may electrically couple to the ESD 122 via a power cable.The CMS 123 may operatively couple (e.g., via wired or wirelesscommunications) to the ESD 122 and the meter device 124. The CMS 123 maymonitor operational indicators of the ESD 122 from the ESD 122 and thepower consumption of the MD 120 from the meter device 124. For example,the CMS 123 may monitor operational indicators such as: (1) thestate-of-charge (SOC) of the ESD 122; (2) the charging current of theESD 122; (3) the voltage of the ESD 122; and/or (4) the temperature ofthe ESD 122, among others. The CMS 123 may determine and may control,based on the monitored indicators and/or power consumption, a chargingprofile to: (1) reduce charging time of the ESD 122; (2) ensure chargingsafety of the ESD 122; and (3) maintain the ESD's operational life(e.g., battery life).

Although the meter device 124 is illustrated as separate from the ESD122, it is contemplated that the meter device 124 may be integrated withthe ESD 122.

The CMS 123 may include a memory 126, a transceiver 127 and a controller128. The memory 126 (e.g., a non-transitory medium) may store programcode (or instructions) for execution by the controller 128 of controlalgorithms for controlling the MD 120 (e.g., PEV) and for processinginformation from a RFID reader 129. The information from the RFID reader129 to the CMS 123 may be communicated using either wired or wirelesscommunications.

Each of the transceivers 117, 127 and 147 may send communications (usingany protocol including but not limited to TCP/IP and Bluetooth) to othertransceivers 117, 127 and 147 and wireless devices (including the RFIDreader 129, PDAs, notebooks, and laptops (see identification device 260in FIG. 2B)) directly or via the communication network 130. Each of thetransceivers 117, 127 and 147 may receive communications from othertransceivers 117, 127 and 147 and wireless devices directly or via thecommunication network 130.

The RFID reader 129 may be coupled to the mobile connector 121, forexample, via a sleeve or other fastener (not shown) at the mobileconnector 121. By providing the RFID reader 129 at or adjacent to themobile connector 121, the distance between the RFID reader 129 and theRFID tag 119 at the GCP 105 may be minimized and the RFID reader 129 andthe RFID tag 119 of the GCP 105 may be in contact or within a range of10 meters, in this example.

The RFID tag 119, which may be fixed in a predetermined position, mayinclude an integrated directional antenna (not shown) to increase theoperational range of the RFID tag 119 in a predetermined direction(e.g., a direction associated with the MD 120). For example, theoperational range may be increased in the direction associated with apredetermined parking location for a PEV being charged.

Although the RFID reader 129 is illustrated as positioned on the mobileconnector 121, it is contemplated that other positions are possibleincluding at the MD 120 (e.g., on or in the MD or the PEV) or in aportable device in communication (e.g., wired or wireless communication)with the MD 120 or charging station 110.

The RFID tag 119 may be an active RFID tag powered via the gridconnector 115 or a battery (not shown) or a passive RFID tag powered viatransmissions from the RFID reader 129. The RFID tag 119 may be mountedon the grid connector 115 to be read by the RFID reader 129 when theRFID reader 129 is within the operating range of the RFID tag 119 and/orin response to the mobile connector 121 mating with the grid connector115 (e.g., by triggering the RFID reader via a connection closed by themating of the mobile connector 121 and the grid connector 115.

The meter device 124 may measure power (KWh) drawn by the MD 120. Thememory 126 may store meter readings (e.g., measurements) associated withthe initiation and/or end of each charging session to determine thepower consumed (stored) during the charging session. For example, theCMS 123 may read the meter device 124 at the end of each chargingsession and may store the readings in the memory 126. Responsive to theend of a charging session, the CMS 123 may determine the power stored bythe MD 120 and may send the determined power along with other chargingevent information including the RFID tag identification information,time and date, among others to the reconciler 140 via the transceiver127 of the MD 120, the communication network 130 and the transceiver 147of the reconciler 140.

The CMS 123 may send the determined power and charging event informationto the reconciler 140 after each charging event or may send thedetermined power and charging event information to the reconciler 140 atpredetermined times or in response to a triggering command from thereconciler 140.

Although antennas are not shown in FIG. 1 for brevity, each transceiver117, 127 and 147 communicating wirelessly may be coupled to at least oneantenna for such wireless communications.

Although the RFID tag 119 is shown, it is contemplated that any devicewhich uniquely identifies the GCP 105 may be used including a bar code,or other tagging technology such as a unique audio or visual tag and anaudio or image recognition system to uniquely identify the GCP 105.

Although RFID reader 129 is shown, it is contemplated that any devicewhich reads the tag associated with the GCP 105 may be used. It iscontemplated that several different tags may be incorporated into thesystem 100 to each uniquely identify the GCP 105. For example, the tagassociated with the GCP 105 may include both a bar code tag and an RFIDtag such that a reader associated with the MD 120 may read at least oneof the bar code tag or the RFID tag.

The charging station 110 may include a memory 116, the transceiver 117and a controller 118. The memory 116 may store program code forexecution by the controller 118 of control algorithms to control, forexample, communications via the transceiver 117 and the charging of MDs120 via the switch 114. The transceiver 117 may send communications todevices on the communication network 130 (including the MD 120 and/orthe reconciler 140 and may receive communications from these devicesincluding the MD 120 and/or the reconciler 140. The switch 114, based oncontrol signals from the controller 118, may selectively connect theutility grid 150 to the grid connector 115 to enable charging of the MD120 or may selectively disconnect the utility grid 150 from the gridconnector 115 to disable (or block) charging of the MD 120.

Although switch 114 is shown as a one pole switch, it is contemplatedthat other switching configurations are possible to selectively connectthe utility grid 150 to particular circuits of the MD 120 or toselectively disconnect the utility grid 150 from the particular circuitsof the MD 120. It is also contemplated that the power supplied from theutility grid may be multi-phase power (e.g., 2 phase power) and theswitch may include multiple poles corresponding to multiple phases ofthe power and optionally ground.

Although the charging station 110 is shown to be grid-connected, it iscontemplated that the charging station 110 may be connected to any powersource for generating electrical power including: (1) alternatingcurrent (AC) sources such as AC generators; or (2) direct current (DC)sources such as batteries, fuel cells, and photovoltaics, among others.It is also contemplated that an inverter (not shown) may be used with ACsources to convert AC power to DC power prior to charging of the ESD 122of the MD 120.

The reconciler 140 may register the unique identifier tag of thecharging station 110 with a corresponding customer account (not shown).For example, a user may correspond the RFID tag 119 to the gridconnector 115 and may register the RFID tag 119 to the GCP 105 viaregistration software, for example provided from a self service portalvia a web browser application on the Internet.

The reconciler 140 may communicate with a plurality of charging stations110 and MDs 120 to authorize charging sessions using the registeredinformation. For example, after RFID tag information (e.g., a uniqueidentifier of the GCP 105) is read by the MD 120, the RFID taginformation and information identifying MD 120 may be sent to thereconciler 140 for authorization to charge (or discharge) the MD 120.The information may be sent to the reconciler 140 from the MD 120 in acommunication session established between the MD 120 and the reconciler140 via transceiver 127 of the CMS 123 and transceiver 147 of thereconciler 140 and the communication network 130.

Although the reconciler 140 is shown communicating with one MD 120 andone GCP 105, it is contemplated that the reconciler 140 may communicatewith any number of MDs and GCPs. It is also contemplated that thereconciler 140 may perform reconciliation processes for billing accountsassociated with the GCPs that correspond to particular RFID tags.

The MD 120 may receive an authorization code from the reconciler 140 toenable the charging session. The MD 120 may establish a communicationsession between the MD 120 and the charging station 110 (as a directcommunication) via transceiver 127 of the CMS 123 and transceiver 117 ofthe charging station 110, or (as an indirect communication) using thecommunication network 130, transceiver 127 of the CMS 123 andtransceiver 117 of the charging station 110. The MD 120 may communicatethe authorization code to the charging station 110 such that thecontroller 118 of the charging station 110 may control the switch 114 toclose to enable charging of the MD 120.

Although the MD 120 may provide the authorization code to the chargingstation 110, it is contemplated that any set of communications may beused such that the charging station 110 receives authorization directlyor indirectly from the reconciler 140. Although an authorization code isillustrated, it is contemplated that other communication may be used forauthorization of the MD to charge including, for example, a digitalcertificate from the reconciler 140.

The reconciler 140 may include in memory 146 account and billinginformation associated with the MDs 120 in system 100 to determine basedon pre-established rules whether to authorize (e.g., automaticallywithout user input) a charging session including whether an accountassociated with the MD 120 may be active and whether a prepayment or acredit may be associated with the active account.

Although the charging station 110 is illustrated as controlling theswitch 114, it is contemplated that functions of the charging station110 may be provided by the reconciler 140 via the communication network130. For example, the reconciler 140 may control the switch 114 directlyvia a control signal from the reconciler 140 via the communicationnetwork 130.

FIG. 2A is a schematic diagram illustrating a system 200 for identifyinga GCP 105 to the MD 120 in accordance with another exemplary embodiment.

Referring to FIG. 2A, the system 200 may include the GCP 105 (e.g., anelectrical outlet), the MD 120, the communication network 130 and thereconciler 140. The operation of system 200 is similar to the operationof system 100 except that the GCP 105 (e.g., electrical outlet) may notinclude the charging station 110. The electrical outlet 105 iselectrically connected to an electrical supply 150, for example, theelectric utility grid. The electrical outlet 105 may include anelectrical outlet cover 210, an electrical receptacle 216 and an RFIDtag 212.

In certain exemplary embodiments, the RFID reader 129 may be triggeredto communicate with the RFID tags 212 within operational range based onone of the triggering conditions: (1) subsequent to electricalconnection of the mobile connector 121 with the electrical receptacle211 (e.g., based on or responsive to the mobile connector 121electrically connecting to the electrical outlet 105); (2) responsive torelease of a power cable 125 from a power cable storage unit (notshown); (3) responsive to attachment of the power cable 125 to the MD120; (4) responsive to placing the MD 120 in a charging mode; (5)responsive to the MD 120 (e.g., a mobile vehicle) being placed in aparked mode (e.g., in which the transmission is placed in park) and/or(6) responsive to the MD being turned off (e.g., the ignition switch tomobile vehicle 120 being turned off). For example, the controller 128 ofthe MD 120 may control (e.g., trigger) the RFID reader 129 to read theRFID tag 212 (e.g., the unique identification information of RFID tag212) associated with electrical outlet 205 in response to one of thetriggering conditions.

The controller 128 of the MD 120 may communicate via the transceivers127 and 147 and the communication network 130 to the controller 148 ofthe reconciler 140 and may send the RFID tag information and chargingevent information to the reconciler 140 after a charging session ends.The reconciler 140 may adjust the billing account associated with theelectrical outlet 105 based on the charging event information from theMD 120 and may aggregate each charging event associated with the MD 120to one aggregated billing account for the MD 120. For example, the RFIDtag 212 may act as an identifier of the GCP 105 to enable the reconciler140 to adjust the billing account associated with the GCP 105. Arelationship table may be provided in the memory 146 of the reconciler140. The relationship table may correspond the GCP identifiers tocustomer billing accounts.

The reconciler 140 may allow registration of the unique identifier tagof the electrical outlet 205 with a corresponding customer account.

It is contemplated that the billing account associated with the MD 120may be billed at a fixed fee (e.g., a monthly, semi-annual, annual orperiodic fee) and that the adjustment of the billing account associatedwith the GCP 105 may be based on differential meter readings from themeter device 124 of the MD 120 (which corresponds to the energy suppliedby the GCP 105 (electrical outlet) during charging of the ESD 122.

FIG. 2B is a schematic diagram illustrating a system 250 for identifyingthe GCP 105 to the MD 120 in accordance with a further exemplaryembodiment.

Referring to FIG. 2B, the system 250 includes the GCP 105, the MD 120,the communication network 130, and the reconciler 140. The functions ofsystem 250 are similar to those of system 200 except that the mobileconnector 121 may not include an RFID reader 129 and an identificationdevice 260 (e.g., separate from the MD 120) may be used foridentification of an identification tag 212 (e.g., an RFID tag). Theidentification device 260 may be mobile and may include an RFID reader270, a global positioning system (GPS) unit 280 and a transceiver 290.The identification device 260 may be a personal digital assistant (PDA),a notebook computer, a laptop computer or other processing device. Theidentification device 260 may be triggered via the controller 128 of theMD 120 to read the RFID tag 212 using the RFID reader 260. For example,the transceiver 290 may communicate via the communication network 130and the transceiver 127 of the MD 120 to automatically read (withoutuser intervention) the RFID tag 212.

In certain exemplary embodiments, the identification device 260 mayalert the user of the identification device 260 from the controller 128of the MD 120 to move within an operational range of the RFID tag 212and/or to trigger a reading of the RFID tag 212. The GPS unit 280 may beused with the RFID reader 270 to locate the MD 120 during reading of theRFID tag 212. The RFID tag information associated with the GCP(electrical outlet) 105 and the location information from the GPS unit280 may be sent via the transceiver 290, the communication network 130and the transceiver 127 of the MD 120 to the controller 128 of the MD120. The RFID tag information and location information may be stored inthe memory 126 of the MD 120. After a charging session, other chargingevent information (e.g., the power consumed, the peak power consumed,the initial charging time, the charging end time, and/or the date, amongothers) may be associated with the RFID tag information and locationinformation of the electrical outlet 105. The charging event informationmay be sent to the reconciler 140 via the transceiver 127 of the MD 120,the communication network 130 and the transceiver 147 of the reconciler140 to enable the reconciliation of the customer billing accountassociated with the electrical outlet 105 and the customer billingaccount associated with the MD 120.

Although the RFID tag 212 associated with the electrical outlet 205 andthe RFID reader 270 associated with the identification device 260 areshown, it is contemplated that other identification tags and otherreaders may be used. For example, a bar code tag may be used atelectrical outlet 205 and a bar code reader may be incorporated inidentification device 260 to uniquely identify electrical outlet 205 tothe identification device 260 and the MD 120. It is also contemplatedthat the identification device 260 may include an imager (not shown), asthe bar code reader, to image the bar code associated with theelectrical outlet 205. In such a system, the identification device 260or the MD 120 may include recognition software to recognize the bar codeimaged by the imager of identification device 260 to uniquely identifythe bar code associated with the electrical outlet 205.

In certain exemplary embodiments, the RFID reader 129 or 270 maybroadcast a transmission to acquire the unique identifiers of thecharging stations 110 or the electrical outlets 205. Each respectivecharging station 110 or electrical outlet 205 receiving the broadcasttransmission may send a return transmission indicating a uniqueidentifier of the respective charging station 110 and/or the respectiveelectrical outlet 205. The RFID reader 129 or 270 may include a signallevel measurement unit (not shown) that may measure return signalstrength of each return transmission from a respective charging station110 and/or the respective electrical outlet 205 and a closestdetermination unit (no shown) that may determine a closest chargingstation 110 or electrical outlet 205 based on the measured returnedsignal strength of each return transmission.

In certain exemplary embodiments, the RFID reader 129 or 270 may includethe GPS unit 280 for determining a global position of the RFID reader129 or 270 such that the global position of the RFID reader 129 or 320is matched to a closest global position associated with one of therespective charging stations 110 or the respective electrical outlets205 to determine a closest charging station 110 or a closest electricaloutlet 205.

FIG. 3 is a block diagram illustrating a system 300 for managing billingadjustments in accordance with an exemplary embodiment.

Referring to FIG. 3, system 300 may include a telemetry aggregationdatabase 310 (e.g., a vehicle telemetry aggregation database), aregistration unit 320, a credit card processor 330, a portal 340 (e.g.,a self-service portal) and a billing engine 350. Vehicle telemetry 360(or the CMS 123) may provide tagged charging events (e.g., the chargingevent information including the unique identifier of the electricvehicle 120 tagged with the unique identifier from the RFID tag 119 or212 associated with the GCP 105) to the telemetry aggregation database310. The telemetry aggregation database 310 may aggregate the taggedcharging events for each electric vehicle 120 (e.g., the MD) and maysend to the billing engine 350 the tagged charging events based on(e.g., or parsed by) the unique identifier associated with the GCP 105.

An electric vehicle dealer 370 or the vehicle factory may installvehicle telemetry 360 and on-board RFID readers 129 (or barcode readers)in new electric vehicles and service providers may retrofit the vehicletelemetry 360 and the on-board RFID 129 (or barcode readers) to existingelectric vehicles. The electric vehicle dealer 370 (or anotherresponsible entity) may report (or register) the installation of thevehicle telemetry 360 and the on-board RFID readers 129 of a particularelectric vehicle 120 to the registration unit 320 based on a uniqueidentifier associated with the particular electric vehicle. For example,each electric vehicle 120 may have an associated unique identifier whichmay be registered by the electric vehicle dealer 370 to initiallyregister a new billing account associated with the electric vehicle 120.

An electric vehicle customer (or user) 380 may register for a chargingservice from, for example an electric utility, which may aggregate thebilling for charging or discharging of the electric vehicle 120 to aseparate, aggregated billing account associated with the electricvehicle 120. The electric vehicle customer 380 may receive or maypurchase one or more of: (1) tags (e.g., identification tags such asRFID tags and/or barcode tags) to retrofit to existing electrical outletcovers (via adhesive or other fasteners, among others); (2) electricaloutlet covers that include such identification tags and may be retrofitto existing electrical outlets; and/or (3) electrical outlets thatinclude such tags for installation. The electric vehicle customer 380may install or retrofit the tags, electrical outlet covers and/or theelectrical outlets at charging locations where charging may occur andmay register each identification tag to the customer billing account tobe associated with the identification tag.

For example, a user may register the RFID tag 212 to the electricutility meter associated with the GCP 105 or a utility billing accountnumber via registration software to uniquely match the RFID tag 212 tothe billing account of a customer (e.g., to associate the RFID tag 212with the utility meter serving the GCP 105). The registration mayinclude logging into the portal 340 to provide registration informationindicating the correspondence of the RFID tag to the electric meter orbilling account number via a web browser application over, for example,the communication network 130 or the Internet.

The registration information entered by the electric vehicle dealer 370to setup the tag reader identifier of the electric vehicle 120 in theregistration unit 320 may be matched to the unique identifier on the tagreader to verify and to authorize a particular electric vehicle customer380 in the registration unit 320. After the particular electric vehiclecustomer 380 is verified and authorized, the particular electric vehiclecustomer may register each tag identifier associated with a customerbilling account in the registration unit 320.

The electric vehicle customer 380 may associate a credit card account tothe billing account associated with the electric vehicle 120. Theelectric vehicle customer 380 may establish the association using thecredit card processor 330 via the portal 340. For example, a web browsermay be provided with software to enable the association of the creditcard account with the billing account to facilitate payment for orcredit to a credit account in accordance with an agreement for chargingservices (e.g., charging or discharging of the electrical vehicle 120).

The billing engine 350 may receive the aggregated usage of each electricvehicle 120 by the tag identifier from the telemetry aggregationdatabase 310, the registration information associated with the tagreader and the tag identifiers from the registration unit 350 and creditaccount (or debit account) information from the credit processor 330.The billing engine 350 may aggregate the bill adjustments for eachbilling customer associated with tagged charging events using theaggregated usage.

The billing engine 350 may also aggregate the usage associated with thebilling account of the electric vehicle customer 380. For example, whena particular electric vehicle customer 380 charges the electric vehicle120 at GCP 105, the RFID tag 212 having a unique identifier that may beassociated with a relative (e.g., Grandma) of the electric vehiclecustomer 380, the billing engine 350 may adjust the billed consumptionassociated with the billing account of the relative (Grandma) based onany consumption from or any supply of power to the electrical outlet 105(e.g., associated with Grandma's billing account) used or provided bythe electric vehicle 120. The billing engine 350 may also adjust thebilled consumption associated with the electric vehicle 120 based on anyconsumption from or any supply of power to the electric vehicle 120during the billing period.

The billing adjustment to the relative's billing account may be a costor a credit depending on whether the electric vehicle 120 in aggregatefor the tagged events associated with the relative's billing accountduring a billing period consumed power or in aggregate for the taggedevents associated with the relative's billing account supplied power tothe utility grid 150 (or other electric network).

The billing adjustment to the electric vehicle's billing account may bea cost or a credit depending on whether the electric vehicle 120 inaggregate during the billing period consumed power or in aggregatesupplied power to the utility grid 150.

When the electric vehicle customer 380, for example, charges theelectric vehicle 120 at home 395, the same billing adjustment processoccurs for the billing account associated with the home 395 and thebilling account associated with the electric vehicle 120.

The billing adjustment for each tagged changing event associated withthe tag identifiers associated with a particular billing account may beaggregated to generate an aggregated billing adjustment. For example,when two or more electric vehicles 120 use one tag 212 associated with aparticular billing account, the billing engine 350 may generate anaggregated billing adjustment based on the two or more electric vehicles120. It is also contemplated that one or more tags 212 may be associatedwith a common billing account and the tagged charging events associatedwith each of the one or more tags 212 may be aggregated by the billingengine 350.

Although one vehicle telemetry 360 is shown providing tagged chargingevents, it is contemplated that tagged charging events may be receivedfrom any number of electric vehicles with vehicle telemetry.

Although two location have been illustrated for charging of an electricvehicle (e.g., the relative's location 390 and the electric vehiclecustomer's location 395), it is contemplated that the electric vehicle120 may charge at any number of locations having tag identifiers toallow reconciliation of billing accounts.

FIGS. 4A and 4B are a top view illustrating an electrical outlet 205 ain accordance with an exemplary embodiment and a cross-sectional viewillustrating the electrical outlet 205 a along a line A-A.

FIG. 4B, to reduce the complexity, does not show fastener 217 forattachment of an electrical outlet cover 210 a to an electricalreceptacle 216 via fastener recess 214.

Referring to FIGS. 4A and 4B, the electrical outlet 205 a may includethe electrical outlet cover 210 a and a pair of electrical sockets 211integral to the electrical receptacle 216. The electrical outlet cover210 a may include, for example, two openings configured to be closed bythe pair of electrical sockets 211. The electrical outlet cover 210 amay include a fastener opening 218 in a middle portion of the electricaloutlet cover 210 a to fasten via a fastener (not shown) the electricaloutlet cover 210 a to the electrical receptacle 216. The electricaloutlet 205 a may include a housing 215, for example, which may be setinto a wall or other structure such that the electrical receptacle 216may be set at least partially inside the housing 215 with a pair offlanges 219 extending from the housing 215. Fastening holes 220 in theflange 219 may be used with fasteners (e.g., screws) (not shown) tofasten the electrical receptacle 216 to the wall or other mountingstructure.

Although an electrical outlet is shown with a pair of electrical sockets211, it is contemplated that other socket configurations are possibleincluding electrical outlets with any number of sockets or with suchsockets in other relative locations within the housing such as a doublesocket side-by-side configuration, a single socket configuration and/ora triple socket using a vertical, horizontal or triangularconfiguration, for example.

The electrical outlet 205 a may include an RFID tag 212 a mounted onelectrical outlet cover 210 a for communication with the RFID reader 129or 270, for example.

It is contemplated that the RFID tag 212 a may be attached to theelectrical outlet cover 210 a after the electrical outlet cover 210 ahas been fastened to the electrical receptacle 216. For example, theRFID tag 212 a may be retrofit to the electrical outlet 205 a or anexisting conventional electrical outlet after the electrical outlet 205a or the existing conventional outlet is operational.

Although the RFID tag 212 a is shown covering the fastener opening 218,it is contemplated that the RFID tag 212 a may be located anywhere on oradjacent to electrical outlet 205 a as long as the RFID tag 212 a doesnot interfere with one or more of the electrical sockets 211.

Although the RFID 212 a is shown in FIGS. 4A and 4B, it is contemplatedthat a bar code (or bar code tag) may be used instead of the RFID tag212 a or in combination with the RFID tag 212 a. In such a combinationtag, the electronics (not shown) associated with the RFID tag 212 a maybe embedded in RFID tag 212 a and the bar code may be provided on asurface of the RFID tag 212 a to provide the combined functionality ofan RFID tag 212 a and a bar code.

Although the RFID 212 a is illustrated as covering the fastener opening218 and fastener 217, it is contemplated that the fastener 217 (see FIG.4D) may fasten the RFID tag 212 a and electrical outlet cover 210 a tothe electrical receptacle 216.

FIGS. 4C and 4D are a top view illustrating an electrical outlet 205 bin accordance with another exemplary embodiment and a cross-sectionalview illustrating the electrical outlet 205 b along a line B-B.

Referring to FIGS. 4C and 4D, the electrical outlet 205 b may include anelectrical outlet cover 210 b, an RFID tag 212 b and the electricalreceptacle 216. The electrical receptacle 216 is the same as thatdescribed in FIGS. 4A and 4B. The electrical outlet cover 210 b mayinclude a hole 213 closed by the electrical socket 211, another hole 218coincident with the fastener recess 214 of the electrical receptacle 216for fastening with the fastener 217. The electrical outlet cover 210 bmay include a portion 230 b that may be raised above other portions ofthe electrical outlet 205 b and shaped to conform with and to cover oneof the electrical sockets 211. The portion 230 b of the electricaloutlet cover 210 b may cover one of the electrical sockets 211 and maycause the electrical socket 211 to be inaccessible from the front of theelectrical outlet 205 b. The RFID tag 212 b may be embedded in theportion 230 b for reading by the RFID reader 129 and 270. The electricaloutlet cover 210 b may be compatible with a conventional receptacle toretrofit the RFID tag 212 b into a conventional electrical outlet.

In certain exemplary embodiments, a conventional electrical outlet covermay be replaced with a replacement cover (e.g., the electrical outletcover 210 a, 210 b, or 210 c) to enable unique identification of a GCP105 a, 105 b, or 105 c.

Although the RFID tag 212 b is shown in FIGS. 4C and 4D, it iscontemplated that a bar code may be provided instead of or incombination with the RFID tag 212 b.

FIGS. 4E and 4F are a top view illustrating an electrical outlet 205 cin accordance with a further exemplary embodiment and a cross-sectionalview illustrating the electrical outlet 205 c along a line C-C.

Referring to FIGS. 4E and 4F, the electrical outlet 205 c is similar tothe electrical outlet 205 b except that the electrical outlet cover 210c includes a pivotable socket cover 220 to selectively cover (and/orseal) a corresponding electrical socket 211. The socket cover 220 mayinclude a pivot arm 221 which may pivot about a pivot axis 222 toselectively allow access to the corresponding electrical socket 211 whenin an open position and to selectively block access to (e.g., coverand/or seal from the external environment) the corresponding socket 211when in a closed position.

Although one electrical outlet and one pivotable socket cover is shown,it is contemplated that any number of electrical sockets 211 andpivotable socket covers may be included in the electrical outlet 205 c.Each socket cover 220 may selectively cover (and/or seals) acorresponding electrical socket 211.

Although the RFID tag 212 a, 212 b and 212 c are shown attached via thefastener 217 or, for example, adhesively mounted to the electricaloutlet cover, it is contemplated that the RFID tag may be clipped to theelectrical outlet cover or may slidably engage with the electricaloutlet cover via a set of mating grooves (not shown) to hold the RFIDtag. Other configurations having different fasteners are also possible.

Although the electrical outlets shown include a three prong plug andreceptacle configuration generally used to supply 120 Volt AlternatingCurrent (VAC) in the United States, it is contemplated that electricaloutlet for other plug configurations and other country standard may beimplemented including, for example, the 220 VAC standard in Europe andthe 240 volt standard in the United States. For example, theconfiguration may include standards set forth by the National ElectricalManufactures Association (NEMA) and International ElectrotechnicalCommission (IEC) (e.g., standard 60320).

Although the electrical outlets shown do not illustrate a Ground FaultInterrupter (GFI), it is contemplated that the electrical outlets mayinclude a GFI to interrupt power to the MD when a ground fault isdetected.

FIG. 5 is a flowchart illustrating a method 500 of associating chargingevent information with information of an identity tag in accordance withexemplary embodiments.

Referring to FIG. 5, in step 510, an identity tag (e.g., an RFID tag orbar code) may be provided (established) at a GCP 105. In step 520, MD120 may receive identity tag information to uniquely identify the GCP105. In step 530, MD (e.g., mobile charging device 120) may monitor forcharging event information indicating attributes of the charging event.In step 540, mobile charging device 120 may associate the charging eventinformation with identity tag information, as associated information. Instep 550, mobile charging device 120 may send the associated informationfor reconciliation of billing accounts associated with the GCP 105 andthe mobile charging device 120.

FIG. 6 is a flowchart illustrating a method 600 of managing a chargingevent in accordance with exemplary embodiments.

Referring to FIG. 6, in step 610, a unique identity tag may be installedat the charging station 110. In step 620, the MD (e.g., the chargingvehicle) may receive the unique identifier tag information associatedwith the charging station 110. In step 630, the reconciler 140 mayreceive from the charging vehicle 120 the unique identifier taginformation associated with the charging station 110 and informationidentifying the charging vehicle 120. In step 635, the reconciler 140may determine whether the charging vehicle 120 is authorized to chargeat the charging station 110. For example, reconciler 140 may determinewhether the charging vehicle has an active billing account and whetherthe active billing account has sufficient funds available to cover thefees associated with charging the charging vehicle 120.

If the charging vehicle 120 is not authorized to charge at the chargingstation 110, the charging station 110 may maintain the disconnection ofthe charging vehicle 120 from the electric grid 150, in step 640.

If the charging vehicle 120 is authorized to charge at the chargingstation 110, in step 650, the reconciler 140 may send to the chargingstation 110 an authorization for charging of the charging vehicle 120.

Although the authorization may be sent directly to the charging station110 from the reconciler 140, it is contemplated that such authorizationmay be sent in the form of an authorization code or authorizationmessage and may be sent to (routed to) the charging station 110 via thecharging vehicle 120.

In step 660, the charging station 110 may connect the charging vehicle120 to the power supply or utility electric grid 150. In step 670, thecharging vehicle 120 may monitor/store the charging event information(e.g., the energy consumed during power storage by the ESD 122, the peakenergy draw during the charging session, the unique identifier of thecharging vehicle 120 and the GCP 105, the charging session start time,the charging session end time and/or the date of the charging session).In step 680, the charging vehicle 120 may send to the reconciler 140,the charging event information and the associated unique identifier ofthe GCP 105 (e.g., including electric outlet 210 or the charging station110).

In step 690, the reconciler 140 may reconcile the billing accountassociated with the unique identifier of the charging station 110 andthe billing account associated with the vehicle 120 in accordance withthe charging event information. For example, the billing accountassociated with the unique identifier may be charged (or credited): (1)a fixed monthly amount for charging services; (2) a fixed amount percharging session or supply event; or (3) based on actual consumed(supplied) power during each charging session or supply event. Thebilling account associated with the unique identifier of the chargingstation 110 may be adjusted (e.g., credited or debited) based on theactual consumed/supplied power during a charge session or supply eventof the electric vehicle 120.

FIG. 7 is a flowchart illustrating a method 700 of reconciling billingassociated with a charging event in accordance with exemplaryembodiments.

Referring to FIG. 7, the reconciler 140 may receive the charging eventinformation and the associated unique identifier of the charging station110 or the electrical outlet 205 in step 710. In step 720, thereconciler 140 may determine from the charging event information, whichincludes information indicating the energy stored/supplied during thecharging or discharging of the charging vehicle 120, the energy costassociated with the charging event. In step 730, the reconciler 140 maystore charging event information and the determined energy costs as arecord in a reconciliation table (not shown) of memory 146 associatedwith the charging vehicle 120. In step 740, the controller 148 of thereconciler 140 may determine whether each record in the reconciliationtable of the memory 146 associated with a particular charging vehiclehas been read.

For example, if the billing associated with a customer account occursmonthly, records associated with charging events are added to thereconciliation table in the memory 146 for each charging event during arespective month. The information in reconciliation table of memory 146is read out after the end of the billing period to aggregate billingsassociated with each charging event to the customer account associatedwith the charging vehicle 120. If all records in the reconciliationtable have been read, the reconciliation process is ended in step 750.If each record in the reconciliation table is not read, in step 760, thecontroller 148 of the reconciler 140 may determine whether a customeraccount associated with the unique identifier of the charging station110 or electrical outlet 205 is associated with an active customeraccount. If the unique identifier in the current record is notassociated with an active customer account, the record may be skipped instep 770 and processing may transfer to step 740.

In step 780, the reconciler 140 may adjust the bill of the customeraccount associated with the unique identifier of the charging station110 or the electrical outlet 205 based on charging event informationand/or may adjust the bill associated with the charging vehicle 120.Processing may then transfer to step 790. For example, the billadjustment for the customer account associated with the uniqueidentifier of the charging station 110 may be based on a fixedadjustment, or the energy consumed or supplied during the chargingevent. In step 790, the reconciler 140 may adjust the current record tothe next record in the reconciliation table of the memory 146 and maytransfer processing to block 740.

Although billing adjustments have been described as based on consumptionto or supply from the MD, it is contemplated that the adjustment of thebilling accounts (associated with the MD and/or the customer accountassociated with the connection of the vehicle) may be based on one ormore of: (1) the energy stored during the charging event; (2) a timeassociated with the charging event; (3) VAR support associated with thecharging event; and/or (4) whether the mobile charging device or a gridmanager controls charging event parameters including, for example,energy draw.

FIG. 8 is a block diagram illustrating a system 800 for managing energyservices in accordance with exemplary embodiments.

Referring to FIG. 8, system 800 may include a portal 830, a TelemetryReceiver and Energy Service Dispatcher (TRESD) 835, a utility portal840, a Mobile Customer Database (MCD) 845, a Mobile RegistrationDatabase (MRD) 850, a Aggregated Telemetry Database (ATD) 855, a controlprocessor 860, an ancillary services controller ASC 865, a billingengine 870, a Payment Subscription and Lease Unit (PSLU) 875, and a cardprocessor 880.

A mobile device (MD) dealer 810 (e.g., electric vehicle dealer) or theMD factory may install MD telemetry (e.g., vehicle telemetry) includingan on-board RFID reader (and/or barcode reader) in new MDs 815. The MDdealer 810 may install or retrofit smartphones 260 and 815 with RFID orbarcode reading capabilities, for example, by installing: (1) RFIDreaders 270 (or barcode readers) in the smartphones 260 and 815 or byusing imagers of the identification device 260 and 815 to capture animage of a bar code. The smartphones 815 may use image recognitionsoftware to detect the unique identifier associated with the bar code inthe captured image.

The MD dealer 810 (or another responsible entity) including, forexample, a MD customer 805 may report (or register) the installation ofthe MD telemetry and/or the RFID reader 129 or 270 associated with aparticular MD 120 or smartphone 815 using the MD registration portal 832based on a unique identifier associated with the particular MD 120 or815. For example, each MD (and/or smartphone) 120 and 815 may have anassociated unique identifier which may be registered by the MD dealer810 to initially register a new mobile asset account 896 associated withthe MD 120.

The registration information entered by the MD dealer 810 (or MDcustomer 805) to setup the tag reader identifier of the MD 120 in the MDregistration database 850 may be matched to the unique identifier on thetag reader to verify and to authorize a particular MD customer 805 inthe MD customer portal 831. After the particular MD customer 805 isverified and authorized, the particular MD customer 805 may registereach tag identifier (bar code or RFID tag) to a fixed asset account 894(e.g., customer billing account associated with a fixed electric utilitymeter) via the MD customer portal 831 in the MD registration database850.

The MD customer 805 may associate a credit, debit or prepayment account895 to a mobile asset account 896 of the MD 120 for payment/creditassociated with the energy services of the MD 120. The MD customer 805may establish this association in the MD customer database 850 using theMD customer portal 831. For example, a web browser may be provided withsoftware to enable the association of the credit card account 895 withthe mobile asset (e.g., MD) account 896 to facilitate payment for orcredit to a credit account in accordance with an agreement for energyservices (e.g., charging or discharging of the electrical vehicle 120 orother ancillary services).

The MD customer 805 or MD user (e.g., electric vehicle customer) mayregister for renewable energy services, for example, from an electricutility or renewable energy supplier using portal 830. The renewableenergy services may include primary services provided by the renewableenergy source 891 or a power generator including, for example, chargingservices to charge the MD 120 or ancillary services provided by the MD120 including, for example, (1) energy supply services by dischargingthe MD 120; (2) regulating service provided by the MD 120 to regulatethe electric grid 150 in response to power fluctuations caused by therenewable energy source 891 and/or power generators, (2) frequencycontrol services provided by the MD 120 to adjust frequency of theelectric grid 150 in response to under frequency or over frequencyconditions caused by the renewable energy source 891 and/or the powergenerators; and/or (3) VAR control services provided by the MD 120 toadjust power factor in response to a power factor of the electric grid150 below a threshold level.

The MDs or smartphones 120 and 815 may provide tagged connection events(or charging events) (e.g., connection event information including theunique identifier of the MD 120 tagged with the unique identifier fromthe bar code or the RFID tag 119 or 212 associated with the GCP 105) viathe TRESD 835 to the ATD 855. The TRESD 835 may include a plurality ofMD telemetry and dispatch units (MDTDUs) 835-1, 835-2, . . . 835-N withopen or proprietary MD telemetry/communication standard and devicestandard for communication of vehicle telemetry (e.g., real-time or nearreal time vehicle telemetry) between the MDs and/or smartphones 120 and815 and respective MDTDUs 835-1, 835-2, . . . 835-N. For example,MDTDU-1 835-1 may communicate with a first group of MDs 120 using afirst communication/device standard and MDTDU-2 835-2 may communicatewith a second group of MDs 120 using a second communication/devicestandard.

The MD 120 may send its tagged connection events or the smartphone 815may send the associated MDs 120 tagged connection events to theappropriate MDTDU 835-1, 835-2, or 835-N of the TRESD 835. The TRESD 835may provide the tagged connection events to the ATD 855, which mayaggregate the tagged connection events parsed by the unique identifierof the MD 120 and/or parsed by the unique identifier from the bar codeor RFID tag 119 or 212 associated with the GCP 105 (e.g., correspondingto the fixed asset account 894 of the GCP 105). The ATD 855 may formatthe tagged connection event information into a format common for storageof the records (e.g., all records) in the ATD 855.

The ATD 855 may send the aggregated records of the connection events tothe control processor 860, which may provide the aggregated connectionevent information in the format used by the billing engine 870 to adjustthe fixed asset accounts 894 and bill the mobile asset accounts 896.

Although the aggregated connection event information is shown as beingsent via the control processor 860 to the billing engine 870, it iscontemplated that a data interface may be established between the ATD855 and the billing engine 870 to send the aggregated connection eventinformation to the billing engine 870 in a format used by the billingengine 870 to bill customers.

In certain exemplary embodiments, the billing processor may include thebilling engine 870 and the ATD 855 (or an aggregation unit). The ATD855, for example, may: (1) receive for each connection event anindicator indicating at least one of: (i) a device (or asset) identifierof the device (or asset) 120 used during the connection event to realizeenergy service; or (ii) a GCP identifier of the GCP 105 connected to theasset 120 used during the connection event; (2) identify an account thatis associated with the GCP 105 based the indicator; and (3) aggregatethe connection event information in accordance with the identifiedaccounts such that the billing engine 870 may adjust the identifiedaccounts in accordance with (e.g., based on) the aggregated connectionevent information associated with the identified accounts. The ATD 855may store records. Each of the stored records may include at least oneof: (1) a predetermined account associated with each respective asset120 of a fixed asset type and an asset identifier of the respectiveasset 120 of a fixed asset type that identifies the respective asset120; or (2) an account associated with a respective GCP identifier foreach asset 120 of a mobile asset type. The ATD 855, responsive to theindicator not indicating the GCP identifier, may determine (e.g.,identify) the predetermined account that is associated with the fixedasset 120 for realizing the energy service during the connection event.The billing engine 870 may adjust the predetermined account based on adetermined quantity of energy services realized by the asset 120.

The billing engine 870 may aggregate the billing for energy servicesincluding charging or ancillary services of the MD 120 to a separate,aggregated billing account (e.g., the mobile asset account) associatedwith the MD 120 (e.g., electric vehicle). The MD customer 380 or 805 mayreceive or may purchase one or more of: (1) tags (e.g., identificationtags such as RFID tags and/or barcode tags) to retrofit to existingelectrical outlet covers; (2) electrical outlet covers that include suchidentification tags and may be retrofit to existing electrical outlets;and/or (3) electrical outlets that include such tags for installation.The MD customer 380 or 805 may install or may retrofit the tags,electrical outlet covers and/or the electrical outlets at a charginglocation where charging may occur and may register each identificationtag to the customer billing account to be associated with theidentification tag (e.g., a fixed asset account).

For example, a user may register the RFID tag 212 to the electricutility meter associated with the GCP 105 or a utility billing accountnumber via registration software to uniquely match the RFID tag 212 tothe fixed asset account of the customer (e.g., to associate the RFID tag212 with the utility meter serving the GCP 105). The registration mayinclude logging into the portal 340 or 830 to provide registrationinformation indicating the correspondence of the RFID tag to theelectric meter or fixed asset account number via a web browserapplication.

In certain exemplary embodiments, the billing engine 870 may receive theaggregated usage of each electric vehicle 120 parsed by the tagidentifier (associated with a fixed asset account) via the controlprocessor 860 from the ATD 855, and the registration informationassociated with the tag reader 129 or 270 and the RFID tags 119 or 212from the MD registration database 850.

The control processor 860 may receive, via the PSLU 875, credit account(or debit account) information stored in the MD customer database 845 toindicate the financial status of the MD 120 (e.g., mobile asset device).For example, the MD customer 805 may: (1) pay for charging or becredited for ancillary services by using the MD customer portal 831 toestablish a credit account; (2) check the prepayment amount in themobile asset account; and/or (3) increase the prepayment amount usingthe MD customer portal 831. The MD customer 805 may initiate or changeregistered services, for example, from charging services only tocharging and ancillary services, for example.

It is contemplated that different types of bundled services may beoffered including, for example: (1) charging services (e.g., time-of-usecharging or real-time or near real-time control of charging, amongothers), (2) discharging services (e.g., time-of-use discharging orreal-time or near real-time control of discharging, among others); (3)spinning reserve services; (4) regulation services; (4) VAR supportservices; (5) frequency regulation services; (6) capacity services;and/or (7) leasing services (for leasing the MD 120 or ESD 122 of the MD120). It is contemplated that such services may be bundled or may beoffered separately and that the MD customer 805, via the MD customerportal 831, may register for any number of different service offerings.

The billing adjustments (e.g., aggregated billing adjustments) may beposted by the billing engine 870 to the mobile asset accounts 896 and tothe fixed asset accounts 894 for each MD customer 805 and/or for eachfixed asset customer associated with a tagged connection event. The PSLU875 may receive the aggregated adjustments (e.g., charges or credits) tothe mobile asset accounts 896 for each MD customer 805 and may determineother associated charges or credits for each mobile asset account 896.For example, the mobile asset account 896 may have one or more fixedcharges (e.g., periodic charges, such as monthly or annual taxes,subscription charges and/or lease charges, among others). The PSLU 875may post the fixed charges to the appropriate mobile asset accounts 896.

The billing adjustment to a respective mobile asset account 896 may be acost or a credit depending on whether the MD 120 in aggregate had acredit or a cost for energy services realized during the billing period.

In certain exemplary embodiments, the billing engine 870 may provide theaggregated adjustments to the PSLU 875 and the PSLU 875 may post thefixed charges and the aggregated billing adjustments to the mobile assetaccounts 896.

The card processor 880 (e.g., credit, debit and/or prepayment processor)may interface with external financial accounts (e.g., leasers financialaccounts 890 and/or MD financial accounts 895) to debit or credit suchaccounts for the services provided between the MD 120 and system 800. Incertain exemplary embodiments, it is contemplated that the MD customer805 may maintain a prepayment credit in the mobile asset account 896which may be maintained by automatic charges to the MD financial account895.

The billing engine 350 or 870 and/or the PSLU 875 may update the MDcustomer database 845 in real time, periodically or, as requested viathe portal 830 regarding billing information (e.g., including accountbalance, energy service usage by service offering, and/or reconciliationof renewable resource telemetry 892, among others). For example, theupdate information may include: (1) the connection event information;(2) the associated energy services realized at each connection event;and (3) if renewable energy sources 891 are associated with a connectionevent, the type, quantity, and price of the renewable energy sources 891realized by the MD 120 during the connection event. If the serviceoffering is base on real-time pricing of the service, the price may bedetermined by the control processor 860 based on pricing signals sentfrom the utility operator 825 via the ASC 865 or from the renewableresource telemetry 892 of a renewable energy source 891.

In certain exemplary embodiments, the utility operator 825 may set aprice for each energy service offered and may negotiate with powergenerators, renewable energy sources and/or demand side generators andconsumers to satisfy the offered energy services. The utility operators825 may communicate the service offering to the billing engine 350 or870 and/or the PSLU 875 and may provide billing information directly tothe portal 830 upon an authenticated MD customer's request.

The MD customer portal 831 may also provide information regarding thesubscription for one or more services, the terms of the subscription,lease of equipment under the subscription, the location, date and timeof each connection event and/or adjustments for the fixed asset accounts894 for each connection event, among others. It is contemplated thatother information may additionally or, in the alternative, be providedfrom the portal 830 including other information regarding eachconnection event such as: (1) the meter identifier; (2) the MDidentifier; (3) the RFID or barcode identifier; and/or (4) the plugidentifier associated with a respective connection event.

The MD customer portal 831 may be configured to enable downloading ofthe information in one or more common formats (e.g., to enable thecustomer to view and/or analyze to information on a computer) including,for example, sending the information to the MD controller 820 (e.g., inthe MD 120) for display to the MD customer 805 and/or for analysis bythe MD controller 820 to improve operating efficiency of the MD 120 forfuture energy services to be realized. The MD customer portal 831 may beconfigured to directly provide viewing and/or analysis of energyservices information via a web browser for each connection event, foreach energy service over a time specified by the MD customer 805 or inaggregate for the MD customer 805 (e.g., for a plurality of energyservices or for all energy services) based on, for example, user inputfrom the web browser.

FIG. 9 is a flowchart illustrating a method 900 of managing at least onerenewable energy source 891 in accordance with exemplary embodiments.

Referring to FIG. 9, the method 900 may include managing the at leastone renewable energy source 891 for supply of power via the electricgrid 150. In step 910, the renewable energy source 891 may supply powerto MDs 120 via the electric grid 150. In step 920, the control processor860 may control the balancing of the power realized by the MDs 120 withthe supply of power from the renewable energy source 891 using real-timeor near real-time telemetry information from: (1) the MD controllers 820of the MDs 120 and from the renewable resource telemetry 892. Thecontrol processor 860, for example, may control the power realized bythe MDs 120. For example, power output changes from the renewable energysources 891 measured by the renewable resource telemetry 892 may beoffset by controlling the power realized by the MDs 120 connected to theGCPs 105 and/or 205 such that the MDs 120 (e.g., a portion or all of theMDs 120) are controlled to: (1) reduce power consumption from theelectric grid 150; (2) increase the power consumption from the electricgrid 150; (3) reduce power supplied to the electric grid 150; and/or (4)increase the power supplied to the electric grid 150.

The renewable resource telemetry 892 may aggregate telemetry informationinto a common format from any number of renewable energy sources 891 andmay send the renewable resource information in the common format to thecontrol processor 860. The renewable resource information may include aregulation signal, output power, power factor, and/or frequencymeasurements for the renewable energy sources 891. The control processor860, for each respective MD 120 used for balancing of the power on theelectric grid 150 (e.g., the MDs 120 connected to the GCPs 105 or 205),may: (1) determine an operating condition (e.g., operating point or setpoint) for the respective MD 120 in accordance with the measured power;and (2) send the determined operating condition to the respective MD 120via the appropriate MDTDU 835-1, 835-2, . . . 835-N. The MDs 120 thatreceive their determined operating condition may adjust their currentoperating condition to the determined operating condition.

For example, the control processor 860 may continuously monitor themeasured power from the renewable energy source 891 and may: (1)periodically (e.g., repeatedly and/or continuously) determine theoperating conditions for the respective MDs 120; and (2) send thedetermined operating conditions to the respective MDs 120 via theappropriate MDTDU 835-1, 835-2, . . . 835-N. The control processor 860may control the adjustment of the current operating condition of therespective MDs 120 to the determined operating condition for therespective MDs 120 such that the aggregate power realized by the MDs 120follows or substantially follows the power output from the renewableenergy source or sources 891 measured by the renewable resourcetelemetry 892.

In some exemplary embodiments the determination, sending and adjustmentoperations may be repeated based on the measured power from therenewable energy source 891 such that the aggregate power realized bythe MDs 120 substantially follows the generation (output) from therenewable energy source 891.

In certain exemplary embodiments, the control processor 860 may monitorpower from the renewable energy source 891, for example, as a signalfrom the renewable resource telemetry 892. The control processor 860 maysend a signal to each MD 120 used to balance the supply of power on theelectric grid 150 to control (e.g., to adjust) the power realized bythose MDs 120.

Although processing of the determined operating conditions is disclosedas occurring at the control processor 860, it is contemplated that itmay occur at the MDTDU 835. In this exemplary embodiment, the controlprocessor 860 may assign aggregated operating points for each of theMDTDUs 835-1, 835-2, . . . 835-N such that each respective MDTDUs 835-1,835-2, . . . 835-N may determine operating points for their registeredMDs 120 that are connected to the electric grid 150 based on theassigned, aggregated operating point for each MDTDUs 835-1, 835-2, . . .835-N. In certain exemplary embodiments, the MDTDUs 835-1, 835-2, . . .835-N may each send (e.g., periodically or continuously) to the controlprocessor 860 an estimated range for their aggregated operating point(e.g., the power (or power profile over time) to be realized by theiraggregated MDs 120) so that the control processor 860 may determine theproper assignment of aggregated operating points for each of the MDTDUs835-1, 835-2, . . . 835-N.

The MD controller 820 via the meter device may validate with theappropriate MDTDUs 835-1, 835-2 . . . 835-N and/or the control processor860 that the MDs 120 actually adjusted their current operatingconditions to the determined operating conditions. It is contemplatedthat the contractual arrangements between or among the utility operator825, the renewable energy sources 891, the control processor 860, theMDTDUs 835-1, 835-2, . . . 835-N and/or the MDs 120 may includecontractual incentives for adjusting and/or penalties for not adjustingthe current aggregated operating points to the determined aggregatedoperating points to follow the power supply curve of the renewableenergy sources 891.

In certain exemplary embodiments, the MD controller 820 (or CMS 123) mayinclude a communication module (e.g., transceiver 127) for communicationto MDTDUs 835-1, 835-2, . . . 835-N or reconciler 140 for reporting theidentifier (e.g., RFID or barcode identifier) associated with the GCP105 to establish a location of the MD or mobile asset 120 at the GCP 105on the electric grid 150, and to receive one or more operatingconditions for realizing the energy service. The received operatingconditions may be based on the established location of the MD (or mobileasset) 120 on the electric grid 150. The MD controller 820 (or CMS 123)may also include a processor (e.g., controller 128) for operating themobile asset 120 in accordance with the received one or more operatingconditions to realize the energy service.

The communication module 127 may receive a signal indicating one or moreenergy services that are offered to the mobile asset 120 and theprocessor 128 may select one of the offered energy services, as theenergy service to be realized. The processor 128 may be in direct orindirect communications (e.g., via MDTDU 835-1, 835-2, or 835-N) withthe ASC or Energy Service Controller (ESC) 865 such that the processor128 and the ASC or ESC 865 (e.g., controller 867) may negotiate (set) aquantity of the selected energy service to be realized.

In certain exemplary embodiments, the ESC 865 may include a processor148 or 867 and a communication unit 147 for receiving from the mobileasset 120 an indicator. The processor 148 or 867 may: (1) determine alocation of the mobile asset 120 on the electric grid 150 based on theindicator received by the communication unit 147; (2) determine one ormore operating conditions for realizing the energy service in accordancewith at least operating constraints associated with the determinedlocation of the mobile asset 120 on the electric grid 150. Thecommunication unit 147 may send to the mobile asset 120 the determinedone or more operating conditions for realizing the energy service.

In certain exemplary embodiments, the communication unit 147 may receivean indicator indicating one of: (1) an identifier of the asset (e.g.,when the asset is of a fixed asset type); or (2) the identifier of theGCP 105 connected to the asset 120 (e.g., when the asset is of a mobileasset type). The processor 148 may model the electric grid 150 in thevicinity of a predetermined location of the electric grid 150 when theindicator indicates the asset 120, as a fixed asset type, or may modelthe electric grid 150 in the vicinity of the location of the GCP 105 or205 of the electric grid 150 when the indicator indicates the identifierof the GCP 105 or 205 connected to the asset 120.

The control processor 860 and/or the MDTDUs 835-1, 835-2, . . . 835-Nmay select the determined operating condition of each respective MD (ormobile asset) 120 such that at least the operating constraints of theelectric grid 150 and/or each of the MDs 120 may not be exceeded (e.g.,may be satisfied).

In certain exemplary embodiments, the control processor 860 may bedistributed processing in other devices in the system 800, may be aplurality of processors associated with: (1) different renewable energysources 891; (2) different MDTDUs 835-1, 835-2, . . . 835-N; (3)different geographic areas or operating regions of the electric grid150; and/or (4) different billing engines 870, among others. Forexample, the system 800 may include any number of: (1) utilityoperators; renewable energy sources 891, MDTDUs 835; ASCs 865, billingengines 870, and/or databases 845 and 850.

In certain exemplary embodiments, in response to the power outputchanges from the renewable energy sources 891 decreasing, the controlprocessor 860 or the MDTDUs 835-1, 835-2, . . . 835-N may: (1) selectone or more of the MDs 120 that do not have operating constraints whichprevent: (i) a reduction of the power consumption by the MDs 120 fromthe electric grid 150; and/or (ii) an increase of the power supplied bythe MDs 120 to the electric grid 150 and (2) control an adjustment ofthe power realized by the selected one or more MDs 120 to offset thedecreasing power output from the renewable energy sources 891.

In various exemplary embodiments, in response to the power outputchanges from the renewable energy sources 891 increasing, the controlprocessor 860 or the MDTDUs 835-1, 835-2, . . . 835-N may: (1) selectone or more of the MDs 120 that do not have operating constraints whichprevent: (i) an increase of the power consumption by the MDs 120 fromthe electric grid 150; and/or (ii) a decrease of the power supplied bythe MDs 120 to the electric grid 150; and (2) control the adjustment ofthe power realized by the selected one or more MDs 120 to offset theincreasing power output from the renewable energy sources 891.

It is contemplated that the renewable energy source 891 may include oneor more of: (1) a wind generator; (2) a hydroelectric generator; (3) ageothermal generator; (4) a wave generator; (5) a current generator; (6)a photovoltaic generator; and/or (7) a solar thermal generator.

Although the measured power from the renewable energy sources 891 isdisclosed as offset using the MDs 120, any portion of the measured powermay be offset. For example, the electric grid 150 may include one ormore energy storage units and the balancing of the power realized by theMDs 120 with the supply of power from the renewable energy sources 891may be based on the power output by the renewable sources 891 includingpower consumed or supplied by the one or more energy storage units(e.g., net of the contributions from electric grid-connected energystorage units).

In certain exemplary embodiments, the balancing of the power realized bythe MDs with the supply of power from the renewable energy source 891may include the control processor 860 or the MDTDUs 835-1, 835-2, . . .835-N: (1) modeling the supply of power realizable by each respective MD120 based on operating constraints of the electric grid 150 andoperating constraints of the MD 120, as model results; (2) aggregatingthe model results for each respective device 120, as an aggregated modelresult; and (3) comparing the aggregated model result to the measuredoutput of the renewable energy resources 891 or electric grid 150 todetermine an adjustment to the power realized by each of the respectiveMDs 120.

FIG. 10 is a flowchart illustrating a method 1000 of managing renewableenergy services in accordance with exemplary embodiments.

Referring to FIG. 10, the method 1000 may manage renewable energyservices for plug in-vehicles 120. In step 1010, the control processor860 or the billing engine 870 may identify a fixed asset account 894that is associated with the GCP 105 used by at least one plug-inelectric vehicle 120 for realizing power during a connection event. Instep 1020, the plug-in electric vehicle 120 may determine a quantity ofthe energy realized during the connection event. In step 1030, thebilling engine 870 using connection event information from the plug-inelectric vehicle 120 or smartphones 815 associated with the plug-inelectric vehicle 20 may adjust the identified fixed asset account 894based on the energy realized by the plug-in electric vehicle 120 duringthe connection event.

FIG. 11 is a flowchart illustrating a method 1100 of managing renewableenergy services in accordance with other exemplary embodiments.

Referring to FIG. 11, in step 1110, one or more plug-in electricvehicles 120 may be registered via MD registration portal 832 of theportal 830 to a renewable energy account and the registration stored inMD registration database 850. The registration may be completed by theMD dealer/leaser 810 or the MD customer 805 using, for example, uniquesecurity codes associated with the plug-in electric vehicle 120.

In step 1120, the plug-in electric vehicle 120 may be charged at aplurality of the GCPs 105 and/or 205 associated with respectivelydifferent fixed asset accounts 894, as a plurality of charging events.In step 1130, the MDTDU 835, the ATD 855 or the control processor 860may aggregate the energy consumed by the plug-in electric vehicle 120during the plurality of charging events (e.g., for a billing period)and, in step 1140, the PSLU 875 and/or billing engine 870 may bill therenewable energy account 896 (e.g., mobile asset account) based on theaggregated energy consumed.

Although FIG. 11 refers to the charging of a plug-in electric vehicle120, it is contemplated that the plug-in electric vehicle 120 may beprovided with or may provide other energy services including ancillaryenergy service such as discharging to the electric grid 150 and gridregulation services, such as frequency regulation service and spinningreserve service, among others.

Although one MD controller 820 is shown providing tagged connectionevents, it is contemplated that tagged connection events may be receivedfrom any number of electric vehicles with vehicle telemetry.

FIG. 12 is a flowchart illustrating a method 1200 of managing energyservices in accordance with exemplary embodiments.

Referring to FIG. 12, the method 1200 may manage energy service for afirst type of asset 120 (e.g., mobile assets) that are connected to theGCPs 105. In step 1210, a respective asset of a first type 120 (e.g., amobile asset or MD) may report an identifier associated with a GCP 105.The identifier may establish a location of the respective asset of thefirst type 120 at the GCP 105 on the electric grid 150. In step 1220,the respective asset of the first type 120 may receive one or moreoperating conditions for realizing the energy service. The receivedoperating conditions may be based on the established location of therespective asset of the first type 120 on the electric grid 150. In step1230, the respective asset of the first type 120 may be operated inaccordance with the received one or more operating conditions to realizethe energy service.

It is contemplated that different classes or types of assets may beestablished such that operations for energy services associated withdifferent classes or types may vary. For example, the assets may beclassified into mobile and fixed assets based on the mobility of anasset (e.g., whether the asset can move from one GCP 105 to another GCP105). As other examples, the assets may be classified based on energystorage/consumption capability, ramp rates, time-of-use, and/or energyservice capabilities, among others.

In certain exemplary embodiments, a mobile asset 120 may receive asignal indicating one or more energy services that are offered to themobile asset 120 and the mobile asset 120 may select one of the offeredenergy services, as the energy service to be realized.

In various exemplary embodiments, the mobile asset 120 in communicationwith (e.g., negotiating with) the ASC 865 may set a quantity of theselected energy service to be realized and the ASC 865 may control(e.g., provide operating conditions for) the mobile asset 120 to achievethe set quantity of the selected energy service.

The energy services (or ancillary services) offered, for example, mayinclude: (1) a service to provide power from the mobile asset 120 to theGCP 105; (2) a spinning reserve service from the mobile asset 120; (3) afrequency support service from the mobile asset 120; (4) a regulationservice from the mobile asset 120; and/or (5) a VAR support service fromthe mobile asset 120.

In certain exemplary embodiments, the ASC 865 may establish the locationof the mobile asset 120 at the GCP 105 on the electric grid 150, maydetermine the one or more operating conditions for realizing the energyservice based on at least the established location of the mobile asset120 on the electric grid 150 (e.g., electrical connection of the mobileasset 120 to the electric grid 150), and may send to the mobile asset120 the determined one or more operating conditions for realizing theenergy service. The one or more operating conditions may be determinedin accordance with at least one operating constraint associated with thelocation of the mobile asset 120 on the electric grid 150.

FIG. 13 is a flowchart illustrating a method 1300 of managing energyservices in accordance with further exemplary embodiments.

Referring to FIG. 13, the method 1300 may manage energy service for themobile asset 120 connected to the GCP 105 of the electric grid 150. Instep 1310, the ASC 865 (or ESC) may receive an indicator indicating, forexample, an identifier for the GCP 105 connected to the asset 120 or theidentifier of the asset itself. In step 1320, the ASC or ESC 865 mayreference the indicator to determine a vicinity of the asset on theelectric grid 150. For example, the indicator may be matched withidentifiers in the lookup table 866.

In step 1330, the ASC or ESC 865 may generate a control signal includingcontrol information (or operation conditions) for realizing the energyservice. The control signal information may be based on operatingconstraint of the electric grid 150 in a vicinity of the asset 120 andoperating constraint indicated by the received indicator. For example,the ASC or ESC 865 may model the electric grid 150 in a vicinity of thelocation of the mobile asset 120 based on the present operatingparameters/conditions of the electric grid 150 (e.g., the voltagesand/or currents at different points on the electric grid 150 and theelectrical properties of the components of the electric grid 150 (e.g.,I-V characteristics, thermal characteristics, maximum steady-stateratings and/or peak ratings (operating currents and voltages), amongothers))). The vicinity of the location of the mobile asset generallyrefers to a portion of the electric grid 150 electrically surroundingthe mobile asset 120 that is sufficiently large to ensure that operationof the mobile asset 120 within the established operating conditions doesnot cause operational failures of grid equipment or the mobile asset120. The modeling by the ASC or ESC 865 may determine the energyservices to be supplied or consumed by the mobile asset 120 to operatethe electric grid 150 in the vicinity of the GCP 105 at nominal voltagesand/or current levels without exceeding ratings of the equipment (e.g.,transformer and line ratings) in the electric grid 150 and/or withoutexceeding ratings for the mobile asset 120.

The modeling may include simulations to verify that the mobile asset 120may: (1) charge or discharge at a particular level or within aparticular range of levels within operating constraints of the electricgrid 150 (such that overcurrent, and/or overvoltage or undervoltageconditions, among others, do not occur on the electric grid 150); and/or(2) provide particular services (such as frequency stability, VARsupport, voltage regulation, or/and voltage support, among others). TheASC or ESC 865 may obtain further operating constraints from the mobileasset 120 and may provide operating conditions (or operating set points)for the mobile asset 120 in accordance with the operating constraintsobtained from the mobile asset 120 and/or the operating constraints ofthe electric grid 150. For example, the mobile asset 120 may constrainthe charging of the mobile asset 120 to: (1) a particular time-of-day;(2) a maximum charging current; (3) a maximum charging capacity; and/or(4) different charging or discharging ranges based on charge level ofthe ESD 122 or based on expected use of the mobile asset 120.

In step 1340, the ASC or ESC 865 may send to the mobile asset 120, thecontrol signal.

In certain exemplary embodiments, the ASC or ESC 865 may include thelookup table 866 (or database) for storing records. Each of the recordsmay include (1) an identifier associated with a respective GCP 105 or205; and (2) a location (e.g., electrical connection) of the respectiveGCP 105 on the electric grid 150. The ASC or ESC 865 may reference thelocation of the mobile asset 120 on the electric grid 150 based on anidentifier of the GCP 105 received from the mobile asset 120 by usingthe lookup table 866. For example, the lookup-table 866 may associatethe respective GCP 105 with a point on the electric grid (e.g., alow-voltage side transformer connection). The ASC or ESC 865 may controlthe operating conditions of the mobile asset 120 in accordance with themodeling results.

FIG. 14 is a flowchart illustrating a method 1400 of managing energyservices in accordance with other exemplary embodiments.

Referring to FIG. 14, the method 1400 may manage energy services for themobile asset 120 connected to the GCP 105 during a connection event. Instep 1410, the mobile asset or mobile assets 120 may determine aquantity of the energy services realized during the connection event. Instep 1420, the control processor 860 may identify an account associatedwith the GCP 105 used during the connection event by matching anidentifier associated with the GCP 105 (e.g., of the RFID or barcode tag212) with the associated fixed (billing) account via the MRD 850. Instep 1430, the billing engine 870 may adjust the identified accountbased on the quantity determined by the mobile asset 120.

In various exemplary embodiments, the identification of the account thatis associated with the GCP 105 includes: positioning RFID reader 129 or270 in an operating range of an identification tag 119 or 212 associatedwith the GCP 105 that is used by the respective asset 120 for the energyservice during the connection event; reading, by the identificationmodule 129 or 270 from the identification tag 119 or 212, the identifierof the GCP 105; and referencing the identifier of the GCP 105 with theaccount that is associated with the GCP 105.

In certain exemplary embodiments, the mobile asset 120 may be registeredto a mobile asset account 896 and may determine further quantities ofenergy services realized during further connection events such that therealized energy services of the mobile asset 120 may be aggregated forbilling of the mobile asset account 896.

FIG. 15 is a flowchart illustrating a method 1500 of managing energyservices in accordance with additional exemplary embodiments.

Referring to FIG. 15, the method 1500 may manage energy service for anasset 120 connected to the GCP 105 of the electric grid 150. In step1510, the ASC or ESC 865 may receive from the asset 120 (e.g., a mobileasset or a fixed asset) an indicator indicating at least one of: (1) anidentifier associated with the asset 120; or (2) an identifier of theGCP 105 connected or coupled to the asset 120. In step 1520, the ASC orESC 865 may determine a location of the asset 120 on the electric grid150 based on the received indicator (for example, using the lookup table866). In step 1530, the ASC or ESC 865 may determine one or moreoperating conditions for realizing the energy service based on at leastthe determined location of the asset 120 on the electric grid 150. Instep 1540, the ASC or ESC 865 may send to the asset 120, the determinedone or more operating conditions for realizing the energy service.

In step 1550, the ATD 855 or billing engine 870 may identify an accountthat is associated with the GCP 105 based on the indicator. In step1560, the billing engine 870 may adjust the identified account based ona quantity of energy services realized by the asset 120 in accordancewith the determined one or more operating conditions.

For example, the indicator may indicate the asset identifier of theasset 120 and that the asset is stationary, substantially non-moveableor fixed asset or may indicate the identifier of the GCP 105 for theasset 120 and that the asset is a mobile asset (e.g., capable of movingfrom one GCP 105 to another GCP 105). Responsive to an indication of theasset identifier, the ASC or ESC 865 may search in the look-up table 866for a predetermined location associated with the asset identifier.

In various exemplary embodiments, the ASC or ESC 865 may send a signalindicating one or more energy services that are offered to the asset 120and may receive from the asset 120 a selection of one of the offeredenergy services, as the energy service to be realized. The selection maybe automatic (e.g., without user intervention) based on the operatingstatus of the asset 120 or the selection may be by a user via a servicenotification, for example, using the smartphone 815 or via a display ofthe asset 120.

In certain exemplary embodiments, the asset 120 (e.g., fixed or mobileasset) may receive one or more operating conditions from the ASC or ESC865 for realizing the energy service. The received operating conditionsmay be based on one of: (1) a predetermined location of the asset 120,for example, when the asset is a fixed asset; or (2) the locationassociated with the GCP 105 connected to the asset 120, for example,when the asset 120 is a mobile asset.

FIG. 16 is a flowchart illustrating a method 1600 of managing energyservices in accordance with further exemplary embodiments.

Referring to FIG. 16, the method may manage energy service for aplurality of assets 120 of different types connected to the GCPs 105. Instep 1610, a respective asset 120 of the plurality of assets 120 maydetermine a quantity of the energy service realized by the respectiveasset 120 during a connection event. In step 1620, responsive to therespective asset 120 being of a first type (e.g., a mobile type),detecting an identifier of the GCP 105 that identifies the GCP 105associated with the respective asset 120 of the first type used for theconnection event. In step 1630, the respective asset 120 may sendconnection event information including, for example, at least one of:(1) the determined quantity of the energy service and the assetidentifier that identifies the respective asset 120 responsive to therespective asset 120 not being of the first (mobile) asset type; or (2)the determined quantity of the energy service and the detected GCPidentifier, responsive to the respective asset 120 being of the first(mobile) asset type.

In certain exemplary embodiments, the quantity to be realized of theselected one of the energy services may be set: (1) by the asset 120;(2) by the ASC or ESC 865; or (3) via negotiation of the ASC or ESC 865and the asset 120 such that the ASC or ESC 865 may then control therespective asset 120 to achieve the set quantity of the selected energyservice.

In certain exemplary embodiments, responsive to (or when) the connectionevent information does not including the GCP 105 identifier, the ASC orESC 865 may identify a predetermined account that is associated with therespective asset 120 for realizing the energy service during theconnection event; and the billing engine 870 may adjust thepredetermined account based on the quantity determined by the respectiveasset 120.

FIG. 17 is a flowchart illustrating a method 1700 to manage renewableenergy services in accordance with yet other exemplary embodiments.

Referring to FIG. 17, the method 1700 may manage energy service for aplurality of the assets 120 of different types connected to GCP 105. Instep 1710, the respective asset 120 may report connection informationincluding an asset identifier of the respective asset 120 (responsive tothe respective asset 120 being connected to the GCP 105). In step 1720,the respective asset 120 may receive one or more operating conditionsfor realizing the energy service. The received operating conditions maybe based on a predetermined location of the respective asset 120 on theelectric grid 150. In step 1730, the respective asset 120 may beoperated in accordance with the received one or more operatingconditions to realize the energy service.

FIG. 18 is a flowchart illustrating a method 1800 to manage energyservices in accordance with yet additional exemplary embodiments.

Referring to FIG. 18, the method 1800 may manage energy service for amobile asset 120 connected to the GCP 105 of an electric grid 150. Instep 1810, the ASC 865 may receive an identifier associated with the GCP105 connected to the mobile asset 120. In step 1820, the ASC 865 maydetermine a location of the mobile asset 120 on the electric grid 150based on the received identifier. In step 1830, the ASC 865 maydetermine one or more operating conditions for realizing the energyservice in accordance with at least operating constraints associatedwith the determined location of the mobile asset 120 on the electricgrid 150. In step 1840, the ASC 865 may send to the mobile asset 120 thedetermined one or more operating conditions for realizing the energyservice.

FIG. 19 is a flowchart illustrating a method 1900 to manage an electricgrid in accordance with other exemplary embodiments.

Referring to FIG. 19, the method 1900 may manage the energy services ofelectric grid 150 having a plurality of MDs 120. The MDs 120 may includean energy storage unit 122 and may be connected to a respective GCP 105to realize energy services. In step 1910, each respective MD 120 mayreport a connection of the respective MD 120 to the GCP 105 andconstraints of the respective MD 120 for realizing the energy services.In step 1920, the MD 120 may receive authorization for the energyservices to be realized based on at least the reported constraints fromthe respective MD 120. In step 1930, the MD 120 may realize theauthorized energy services.

In certain exemplary embodiments, the ASC 865 may determine constraintsof the electric grid 150 for realizing the energy services based on theGCP 105 associated with the connection. For example, the ASC 865 mayprovide authorization to the MD 120. The authorization may includesetting the energy services to be realized based on the reportedconstraints from the MD 120 and the determined constraints determined bythe ASC 865.

In certain exemplary embodiments, the MD 120 may permit the realizing ofthe energy services in response to energy services that satisfy thereported constraints and may block realizing of the energy services inresponse to energy services that do not satisfy the reportedconstraints. For example, the authorizing of the energy services to berealized for each respective MD 120 may include modeling, by a modelingunit, behaviors of the plurality of connected MDs 120 and the electricgrid 150 to determine the energy services to be realized by eachrespective, connected MD 120.

Although exemplary embodiments have been described in terms of a mobiledevice, a mobile asset or a plug-in electric vehicle having an energystorage device, it is contemplated that such assets may not include anenergy storage device. In such cases, the mobile asset may adjustcurrent draw from the electric grid to provide energy services to theelectric grid.

Although exemplary embodiments have been described in terms of a mobiledevice, a mobile asset or a plug-in electric vehicle, it is contemplatedthat other assets, such as fixed assets (e.g., substantially non-movableasset) may be offered energy services. It is also contemplated that amixture of asset (e.g., fixed and mobile) may be offered such energyservices to allow the assets (all of the assets) of a particular entityto be offered energy service regardless of the GCP of the assets.

FIG. 20 is a block diagram illustrating a system using the exemplaryadapter in accordance with exemplary embodiments.

Referring to FIG. 20, the adapter 2010 may include: (1) an adapterhousing 2020; (2) an electric grid connector 2030 for selectivelycoupling to or decoupling from the electric grid 150 via the electricoutlet or the GCP 105; (3) an electric device connector 2040 forselectively coupling to or decoupling from the electric device 120 (orelectric asset including, for example, fixed or mobile asset types); and(4) embedded circuitry 2050 including a processing unit 2060 and ametering unit 2052. The processing unit 2060 may include, acommunication unit 2053, a timing unit 2054, memory 2055, and anidentification unit 2056 and a processor 2057. In an embodiment, theelectric grid connector 2030 comprises RFID reader 129. The electricgrid connector 2030 and the electric device connector 2040 may bedirectly connected to form a feed through connection therebetween. Forexample, the adapter 2010 may be disposed intermediate to the GCP 105and the electric device 120 and may include the electric grid connector2030 (e.g., a first matting connector) configured to selectively,electrically couple to the GCP 105 and the electric device connector2040 (e.g., a second matting connector) electrically coupled to thefirst matting connector. The second matting connector may be configuredto selectively, electrically couple to the electric device 120. Theembedded circuitry 2050 may be an integrated circuit or may include aplurality of interconnected circuits.

The processor 2057 may control operations of the adapter 2010. Forexample, the processor may control monitoring, by the metering unit2052, of the energy services realized (e.g., the power consumption orsupply of power by the electric device 120). The processor may beconnected (or coupled) to the other units, such as the metering unit2052, the communication unit 2053, the timing unit 2054, the memory2055, and the identification unit 2056) separately for control andcommunications of these units.

Although the processor 2057 is shown separately coupled to the meteringunit 2052, the communication unit 2053, the timing unit 2054, the memory2055, and the identification unit 2056, it is contemplated thatalternatively a shared communication bus may be used.

In certain exemplary embodiments, the processor 2057 may communicate(e.g., bi-directional communications) externally with other device(e.g., the reconciler 140, ESC 865 and/or the electric device 120) viathe communication unit 2053. For example, the processor may communicatewith the electric device 120 to receive operating constraints and/oroperating information (e.g., any operating constraints, operationalparameters or other operational information, among others) of theelectric device 120 such as: (1) state-of-charge constraints; (2)charging current constraints; (3) voltage constraints; (4) temperatureconstraints; (5) present state-of-charge; (6) present voltage; and/or(7) present thermal reading, among others. The communication unit 2053may receive the operating constraints or operating information of theelectric device 120 in a first communication protocol of (e.g.,recognized and used by) the electric device 120 and may either relay(e.g. directly report without processor 2057 intervention) the operatingconstraints and/or operating information of the electric device 120 tothe reconciler 140 (e.g., when the communication protocol of thereconciler 140 is the same as the first communication protocol of theelectric device 120) or may translate (e.g., convert) the operatingconstraints and/or operating information of the electric device 120 intoa second communication protocol of the reconciler 140 (e.g., when thecommunication protocol of the reconciler 140 is not the same as thecommunication protocol of the electric device 120). In this way, theadapter 2010 may provide a communication protocol conversion to enableelectric devices 120 of a particular communication protocol tocommunicate with reconcilers 140 of new or different communicationprotocols.

In response to the reports of the operating constraints (and/oroperating information) by the communication unit 2053 from the adapter2010, the reconciler 140 or the ESC 865 may send to the communicationunit 2053 of the adapter 2010 an energy service signal indicating one ormore operating points (e.g., set points or operating conditions) foroperation of the electric device 120. The communication unit 2053 maycommunicate the indicated one or more operating set points to theelectric device 120 via the communication protocol of the electricdevice 120. The energy service signal may be updated based on ananticipated energy service level of the electric device 120. Thecommunication unit 2053 may communicate the updated or adjusted one ormore operating set points to the electric device 120.

In certain exemplary embodiments, the anticipated energy service levelmay be determined by the reconciler 140 or the ESC 865 based on at leastthe reported quantity of the energy service realized by the electricdevice 120 and the reported operating constraints of the electric device120. The anticipated energy service level may be further determinedbased on reported quantity of the energy service anticipated for theelectric grid 150 and/or reported operating constraints of the electricgrid 150.

In response to or after receiving the reported electric deviceinformation (e.g., the quantity of the energy service realized by theelectric device 120 and/or the operating constraints (e.g., includingcurrent, voltage and/or thermal constraints) of the electric device120), the reconciler 140 or ESC 865, based on the electric deviceinformation, may determine and may control power consumption to orsupply of power from the electric device 120 and/or a charging ordischarging profile of the electric device, for example: (1) to manage(or reduce) the charging time of the ESD 122; (2) to ensure charging ordischarging safety of the ESD 122; and/or (3) to maintain the ESD'soperational life (e.g., battery life).

The metering unit 2052 may be configured to be disposed in the adapterhousing 2020 and may measure: (1) one or more voltages associated with(e.g., between or among) the power conductors of the electric device120; (2) one or more currents associated with (e.g., flowing through)the power conductors of the electric device 2010.

In certain exemplary embodiments, the metering unit 2052 may include oneor more current sensors (such as current transformers (CTs) and/or Hallsensors, among others), one or more voltage sensors (such as potentialtransformers (PTs) and/or voltage probes, and/or one or more thermalprobes, among others.

In certain exemplary embodiments, the voltages and/or the currents maybe measured at the power conductors of the electric device 120. Inalternative exemplary embodiments, the voltages and/or currents may bemeasured from the conductors disposed in the adapter 2010 that connectsthe electric grid connector 2030 and the electric device connector 2040.

The metering unit 2052 may measure a quantity of energy servicesrealized by the electric device 120. For example, in response to aselection of an energy service which charges or discharges the electricdevice 120, the metering unit 2052 may measure the energy (or power)consumed by the electric device 120 or the energy (or power) supplied tothe electric grid 150.

In another example, in response to a selection of an energy service forregulating the electric grid 150, the metering unit may register thecharging and/or discharging profile of the electric device 120 and thetiming unit 2054 may register the timing of this profile. The meteringunit 2052 may send the charging and/or discharging profile (e.g.,voltage and current profiles of the electric device 120) to theprocessor 2057 and the timing unit 2054 may send the timing informationassociated with the electric device 120 providing the regulationservices to the processor 2057. The timing information provided by thetiming unit 2054 to the processor 2057 may be matched with the meteringinformation from the metering unit 2053 to generate a timed profile ofthe energy services realized by the electric device 120. The timedprofiles may be stored in the memory 2055 and/or may be reported to thereconciler 140 or ESC 865. The reconciler 140 or ESC 865, afterreceiving the timed profile of the energy services realized, maydetermine the appropriate compensation for the electric device 120 basedon negotiated contract terms or governmental tariffs.

It is contemplated that other energy services, such as frequency supportor VAR support, may be implemented with similar timed profiles and thatthe metering unit 2052 is configured to provide the appropriatemeasurements, which are subsequently reported as timed profiles to thereconciler 140 or the ESC 865.

The memory 2055 may be coupled to processor 2057. The memory 2055 maystore program code to execute the functionality of the adapter 2010 andmay store or cache connection event information and/or timed profileinformation to enable communication of the information with thereconciler 140 or ESC 865.

In certain exemplary embodiments, the metering unit 2053 may measurepower (KWh) drawn by the electric device 120. The memory 2055 may store,for example, meter readings (e.g., or other measurements) associatedwith the initiation and/or end of each charging session to determine thepower consumed (stored) during the charging session. For example, theprocessor 2057 may read the metering unit 2052 at the end of eachcharging session and may store the readings in the memory 2055. Theprocessor 2057 may store the meter reading with timing information fromthe timing unit 2056 to indicate the beginning and/or ending of theconnection event period. For example, the timing unit 2054 may provideor determine a time, a time range and/or date of a connection event andmay send the time, the time range and/or date to be stored in the memory2055. The memory may store the timing information together with theconnection event information. Responsive to the end of a connectionevent session (e.g., a charging or discharging session), the processor2057 may send the connection event information including the RFID tagidentification information, and the timing information to the reconciler140 or ESC 865 via the communication unit 2053.

The identification unit 2056 may function summarily to (or the same as)an RFID or barcode reader (e.g., RFID reader 129 or 270) to identify theGCP 105 via the identification tag 119 or 212. For example, theidentification unit 2056 may detect (e.g., or read) the identificationtag information or identifier associated with the GCP 105 electricallyconnected or coupled to the electric device 120 and may send theidentification tag information or identifier to be stored in the memory2055. The information associated with each connection event may bestored together as respective records of connection event information.In an embodiment, the GCP 105 may also include an RFID reader 270 and apower sensor module 219.

Although the adapter is described as including separate interconnectedoperational units, it is contemplated that the processor, the timingunit, the metering unit and the communication unit may have otherconfigurations including configurations in which some or all of theseunits are integrated together. For example, the communication unit 2053may be coupled directly or indirectly to (or may be integrated in asingle unit with) at least the identification unit 2056 and the meteringunit 2052.

In certain exemplary embodiments, the processor 2057 may receive: (1) anoffer of energy services to be realized by the electric device 120 fromthe reconciler 140 or ESC 865 and (2) one or more operating constraints(or operating information including operational parameters andanticipated settings or usage) from the electric device 120. Theprocessor 2057 may select one of the offered energy services, as theselected energy service to be realized by the electric device 120 basedon the received one or more operating constraints received from thedevice. For example, the adapter may select the energy service based onone or more weighted factors including: (1) the anticipated profitmargin for the realized electric service; (2) the anticipated orhistorical usage of the electric device 120 by the owner or user of theelectric device 120, (3) the safety parameters specified for theelectric device 120; (4) the anticipated incremental maintenance of theelectric device 120 associated with the realized electric service and/orthe anticipated capability of the electric device 120 (e.g., based onthe energy capacity of the ESD 122) after the energy service isrealized. The weighting factors may be predetermined based on userpreferences, preset, or user selectable based on responses from inquiresto a user interface such as the user interface of the smartphone 815 orMD controller 825.

The processor 2057 may determine the selected energy service and maynotify using the communication unit 2053 the reconciler 140 or the ESC865 of the selected energy service. In other exemplary embodiments, theselection of energy service may be determined by the reconciler 140 orESC 865 based on: (1) the one or more operating constraints provided bythe adapter; (2) usage profiles of the electric device 120 stored in theadapter 2053; and/or stored information of the reconciler 140 or the ESC865 such as electric service rates and anticipated quantities for eachelectric service offered.

In certain exemplary embodiments, in response to the processor 2057reporting the quantity of energy services realized by the electricdevice 120 during the connection event, the reconciler 140, the ASC 865or the billing engine 870 may adjust and may bill an adjustment of afixed account 894 associated with an identifier of the GCP 105 (when theelectric device 120 is of a mobile type) or may adjust and may billanother account 894 (e.g., a predetermined fixed account associated withthe electric device 120 (when the electric device 120 is of a fixedtype)).

In certain exemplary embodiments, in response to the processor 2057reporting the quantity of energy services realized by the electricdevice 120 during the connection event, the memory 2055 may store thequantity or quantities of energy services realized for a particularelectric device 120. The reconciler 140, the ASC 865 and/or the billingengine 870 may adjust and may bill an adjustment of the fixed account894 associated with an identifier of the GCP 105 (when the electricdevice 120 is of a mobile type) or may adjust and may bill anotheraccount 894 (e.g., a predetermined fixed account associated with theelectric device 120 (when the electric device 120 is of a fixed type)).

FIG. 21 is a schematic diagram illustrating an exemplary adapter 2110coupled to an electric device 120 for realizing energy services inaccordance with other exemplary embodiments. FIG. 22 is a partial viewof region A of FIG. 21 illustrating the exemplary adapter 2110.

Referring to FIGS. 21 and 22, the adapter 2160 may include a housing2120, the processor 2057, the communication unit 2053, the timing unit2054, the identification unit 2056, and the metering unit 2052 (e.g.,the detection unit). As shown in FIG. 21, electric grid connector 2030may include the RFID reader 129. The operation of the units in adapter2110 are the same as those of adapter 2010 except that adapter 2010 isconfigured to be intermediate (e.g., in series) between the electricdevice 120 and the GCP 105 or 205 and adapter 2110 is configured to bedisposed around the power conductors 2150 of the electric device 120.For example, the housing 2120 may be configured to be coupled to and tosurround power conductors 2150 of the electric device 120 (e.g., the MDor the electric asset). The metering unit 2052 may be disposed in theadapter housing 2120 to detection currents and voltages associated withthe power conductors 2150.

In certain exemplary embodiments, the housing 2120 may house themetering unit 2052 and in other exemplary embodiments, the housing 2120may house the metering unit 2052, and the processing unit 2060.

The adapter housing 2120 may have a first portion 2120A and a secondportion 2120B. The first portion 2120A may move relative to the secondportion 2120B when opened and the first portion 2120A may be fixedrelative to the second portion 2120B to define a through opening for thepower conductors 2150 when closed. The power conductors 2150 of theelectric device 120 may selectively couple to and may extend through theadapter housing 2120 when the adapter housing 2120 is closed. Forexample, the adapter 2110 may be coupled to the electric device 120 bymoving (e.g., rotating or sliding within a groove) the first portion2120A relative to the second portion 2120B of the adapter housing 2120when the adapter housing is opened to surround power conductors 2150 ofthe device extending through the adapter when the adapter housing 2120is closed.

The metering unit 2052 may include conductor contactors 2135electrically connecting the power conductors 2150 to detect a voltagelevel associated with one or more of the power conductors 2150 of theelectric device 120 and one or more current sensors to sense currentflow in the power conductors 2150 when the power conductors 2150 extendthrough the adapter 2110 and the adapter housing 2120 is closed.

The adapter 2110 may attach to the power conductors 2150 (e.g., a powercord or power cable) such that the adapter 2110 may be configured to bemovable together with the electric device 120.

In various exemplary embodiments, the adapters 2010 and 2110 may,respectively, measure using the metering unit 2502 a quantity of energyservices realized by the electric device 120 may communicate using thecommunication unit to the ESC 865 quantity information of the energyservices actually realized by the electric device 120; and may sendusing the communication unit to the electric device 120, receivedupdated operating set points for the electric device 120 that areupdated by the ESC 865 based on at least the communicated quantityinformation. The updated operating set points may be updated based onthe communicated quantity information and operating constraints of anelectric grid coupled to the electric device 120.

Although the metering unit 2052 is illustrated as separate from theprocessing unit 2060, it is contemplated that the metering unit 2052 maybe integrated with the processing unit 2060.

In other exemplary embodiments, a load switch (not shown) may bedisposed in series with the electric grid connector 2030 and theelectric device connector 2040 to enable cutoff of the electric deviceor asset 120 via the adapter 2010.

FIG. 23 is a flowchart illustrating a method 2300 of managing energyservices using an exemplary adapter 2010 or 2110 in accordance withexemplary embodiments.

Referring to FIG. 23, in step 2310, the method 2300 may manage energyservices for the electric device 120 via the GCP 105 using the adapter2010 or 2110. The GCP 105 may include an identifier. In step 2310, theadapter 2010 or 2110 using the metering unit 2052 may measure a quantityof energy services realized by the electric device 120. In step 2320,the adapter 2010 or 2110 using the identification unit 2056 may detectthe identifier (e.g., identification tag information) of the GCP 105electrically connected to the electric device 120. In step 2330, theadapter 2010 or 2110 may report using the communication unit 2053connection event information including at least: (1) the quantity of theenergy service realized by the electric device 120; (2) an identifier(e.g., stored in memory 2055 of the adapter 2010 or 2110) associatedwith the adapter 2010 or 2110 and (3) the identifier (e.g.,identification tag information) of the GCP 105. The connection eventinformation reported by the adapter 2010 or 2110 enabling adjustment ofaccounts 894 and 896 associated with the adapter 2010 or 2110 and theGCP 105 based on the quantity of energy service realized.

The adapter 2010 or 2110 may report the connection event informationresponsive to the electric device 120 completing a connection event.

FIG. 24 is a flowchart illustrating a method 2400 of managing energyservices using an exemplary adapter 2010 or 2110 in accordance withother exemplary embodiments.

Referring to FIG. 24, the method 2400 may manage energy services by themobile device 120 using the adapter 2010 or 2110. In step 2410, theadapter 2010 or 2110 may receive: (1) an offer for energy services to berealized by the mobile device 120 from the ESC 865 using thecommunication unit 2053; and (2) operation status information of themobile device 120 indicating the operation status of the mobile device120 from the mobile device 120 using communication unit 2053. Thecommunication protocols between the adapter 2010 or 2110 and mobiledevice may be the same protocol as or a different protocol from that ofbetween the adapter 2010 or 2110 and the ESC 865.

In step 2420, the adapter 2010 or 2110 may select one of the offeredenergy services, as the selected energy service to be realized by themobile device 120, based on the received operation status information.

FIG. 25 is a flowchart illustrating a method 2500 of managing energyservices using an exemplary adapter 2010 or 2110 in accordance withother exemplary embodiments.

Referring to FIG. 25, the method 2500 may manage energy services by themobile device 120 via the GCP 105 using the adapter 2010 or 2110. Instep 2510, the adapter 2010 or 2110 may receive using the communicationunit 2053 an energy service signal indicating operating set points forthe mobile device 120. In step 2520, the adapter 2010 or 2110 maycommunicate to the mobile device 120 using the communication unit 2053the indicated operating set points using a communication protocol of themobile device 120.

In certain exemplary embodiments, the adapter 2010 or 2110 may: (1)measure a quantity of energy services realized by the mobile device 120;(2) communicate to the ESC 865 quantity information of the energyservices actually realized by the mobile device 120; and/or (3) send tothe mobile device, received updated operating set points for the mobiledevice 120 that are updated based on at least the communicated quantityinformation. The updated operating set points may be updated based onthe communicated quantity information and operating constraints of theelectric grid 150 coupled to the mobile device 120.

Although exemplary embodiments have been described in terms of a mobileelectric device or a plug-in electric vehicle, it is contemplated thatit may be implemented in software on microprocessors/general purposecomputers such as the computer system 2600 illustrated in FIG. 26. Invarious embodiments, one or more of the functions of the variouscomponents may be implemented in software that controls a computingdevice, such as computer system 2600, which is described below withreference to FIG. 26.

Aspects of the present invention shown in FIGS. 1-25, or any part(s) orfunction(s) thereof, may be implemented using hardware, softwaremodules, firmware, tangible computer readable media having instructionsstored thereon, or a combination thereof and may be implemented in oneor more computer systems or other processing systems.

FIG. 26 illustrates an example computer system 2600 in which embodimentsof the present invention, or portions thereof, may be implemented ascomputer-readable code. For example, systems 100, 200, 250, 300, 800 and2010 of FIGS. 1-3, 8 and 20, can be implemented in computer system 2600using hardware, software, firmware, non-transitory computer readablemedia having instructions stored thereon, or a combination thereof andmay be implemented in one or more computer systems or other processingsystems. Hardware, software, or any combination of such may embody anyof the modules and components used to implement the systems of FIGS.1-3, 8 and 20.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. One ofordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computers linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device.

For instance, at least one processor device and a memory may be used toimplement the above described embodiments. A processor device may be asingle processor, a plurality of processors, or combinations thereof.Processor devices may have one or more processor “cores.”

Various embodiments of the invention are described in terms of thisexample computer system 2600. After reading this description, it willbecome apparent to a person skilled in the relevant art how to implementthe invention using other computer systems and/or computerarchitectures. Although operations may be described as a sequentialprocess, some of the operations may in fact be performed in parallel,concurrently, and/or in a distributed environment, and with program codestored locally or remotely for access by single or multi-processormachines. In addition, in some embodiments the order of operations maybe rearranged without departing from the spirit of the disclosed subjectmatter.

Processor device 2604 may be a special purpose or a general purposeprocessor device. As will be appreciated by persons skilled in therelevant art, processor device 2604 may also be a single processor in amulti-core/multiprocessor system, such system operating alone, or in acluster of computing devices operating in a cluster or server farm.Processor device 2604 is connected to a communication infrastructure2606, for example, a bus, message queue, network, or multi-coremessage-passing scheme.

Computer system 2600 also includes a main memory 2608, for example,random access memory (RAM), and may also include a secondary memory2610. Secondary memory 2610 may include, for example, a hard disk drive2612, removable storage drive 2614. Removable storage drive 2614 maycomprise a floppy disk drive, a magnetic tape drive, an optical diskdrive, a flash memory, or the like.

The removable storage drive 2614 reads from and/or writes to a removablestorage unit 2618 in a well known manner. Removable storage unit 2618may comprise a floppy disk, magnetic tape, optical disk, etc. which isread by and written to by removable storage drive 2614. As will beappreciated by persons skilled in the relevant art, removable storageunit 2618 includes a non-transitory computer usable storage mediumhaving stored therein computer software and/or data.

In alternative implementations, secondary memory 2610 may include othersimilar means for allowing computer programs or other instructions to beloaded into computer system 2600. Such means may include, for example, aremovable storage unit 2622 and an interface 2620. Examples of suchmeans may include a program cartridge and cartridge interface (such asthat found in video game devices), a removable memory chip (such as anEPROM, or PROM) and associated socket, and other removable storage units2622 and interfaces 2620 which allow software and data to be transferredfrom the removable storage unit 2622 to computer system 2600. Computersystem 2600 may also include a communications interface 2624.Communications interface 2624 allows software and data to be transferredbetween computer system 2600 and external devices. Communicationsinterface 2624 may include a modem, a network interface (such as anEthernet card), a communications port, a PCMCIA slot and card, or thelike. Software and data transferred via communications interface 2624may be in the form of signals, which may be electronic, electromagnetic,optical, or other signals capable of being received by communicationsinterface 2624. These signals may be provided to communicationsinterface 2624 via a communications path 2626. Communications path 2626carries signals and may be implemented using wire or cable, fiberoptics, a phone line, a cellular phone link, an RF link or othercommunications channels.

In this document, the terms “computer program medium,” “non-transitorycomputer readable medium,” and “computer usable medium” are used togenerally refer to media such as removable storage unit 2618, removablestorage unit 2622, and a hard disk installed in hard disk drive 2612.Signals carried over communications path 2626 can also embody the logicdescribed herein. Computer program medium and computer usable medium canalso refer to memories, such as main memory 2608 and secondary memory2610, which can be memory semiconductors (e.g. DRAMs, etc.). Thesecomputer program products are means for providing software to computersystem 2600.

Computer programs (also called computer control logic) are stored inmain memory 2608 and/or secondary memory 2610. Computer programs mayalso be received via communications interface 2624. Such computerprograms, when executed, enable computer system 2600 to implement thepresent invention as discussed herein. In particular, the computerprograms, when executed, enable processor device 2604 to implement theprocesses of the present invention, such as the stages in the methodsillustrated by the flowcharts 500, 700, 900, 1000, 1100, 1200, 1300,1400, 1500, 1600, 1700, 1800, 1900, 2300, 2400 and 2500 of FIGS. 5, 7,9-19 and 23-25, discussed above. Accordingly, such computer programsrepresent controllers of the computer system 2600. Where the inventionis implemented using software, the software may be stored in a computerprogram product and loaded into computer system 2600 using removablestorage drive 2614, interface 2620, and hard disk drive 2612, orcommunications interface 2624.

Embodiments of the invention also may be directed to computer programproducts comprising software stored on any computer useable medium. Suchsoftware, when executed in one or more data processing device, causes adata processing device(s) to operate as described herein. Embodiments ofthe invention employ any computer useable or readable medium. Examplesof computer useable mediums include, but are not limited to, primarystorage devices (e.g., any type of random access memory), secondarystorage devices (e.g., hard drives, floppy disks, CD ROMS, ZIP disks,tapes, magnetic storage devices, and optical storage devices, MEMS,nanotechnological storage device, etc.), and communication mediums(e.g., wired and wireless communications networks, local area networks,wide area networks, intranets, etc.).

It is to be appreciated that the Detailed Description section, and notthe Summary and Abstract sections, is intended to be used to interpretthe claims. The Summary and Abstract sections may set forth one or morebut not all exemplary embodiments of the present invention ascontemplated by the inventor(s), and thus, are not intended to limit thepresent invention and the appended claims in any way. Embodiments of thepresent invention have been described above with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined so long as thespecified functions and relationships thereof are appropriatelyperformed.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the invention that others can, by applyingknowledge within the skill of the art, readily modify and/or adapt forvarious applications such specific embodiments, without undueexperimentation, without departing from the general concept of thepresent invention. Therefore, such adaptations and modifications areintended to be within the meaning and range of equivalents of thedisclosed embodiments, based on the teaching and guidance presentedherein. It is to be understood that the phraseology or terminologyherein is for the purpose of description and not of limitation, suchthat the terminology or phraseology of the present specification is tobe interpreted by the skilled artisan in light of the teachings andguidance.

The breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

What is claimed is:
 1. A method of managing at least one renewableenergy source for supply of power via an electric grid, comprising:registering one or more selections of service offerings provided by theat least one renewable energy source selected by customers associatedwith respective mobile devices; supplying power to the mobile devicesfrom the at least one renewable energy source, via the electric grid, inaccordance with the registered customer selections; continuouslymonitoring, by a control processor, power supplied from the at least onerenewable energy source based on telemetry information from a renewableresource telemetry device; determining, by the control processor,aggregated power realized by the mobile devices based on telemetryinformation received by the control processor from telemetry devicesassociated with each of the mobile devices; and offsetting power outputchanges from the at least one renewable energy source with theaggregated power realized by the mobile devices by controlling, with thecontrol processor, current operating conditions of the mobile devices sothat the aggregate power realized by the mobile devices follows orsubstantially follows the power supplied from the at least one renewableenergy source measured from the renewable resource telemetry device,wherein the current operating conditions include operating points of themobile devices and controlling the operating condition includesadjusting in aggregate the operating points of the mobile devices;wherein for each respective mobile device used for balancing of thepower: determining, by a processor, an operating condition for therespective mobile device in accordance with the measured power of the atleast one renewable energy source, wherein the operating condition is anoperating point of the respective mobile device, sending, by theprocessor, the determined operating condition to the respective mobiledevice, and adjusting a current operating point of the respective mobiledevice to the determined operating condition.
 2. The method of claim 1,wherein the offsetting of the power output changes from the at least onerenewable energy source by the power realized by the mobile devices iscontrolled such that each of the mobile devices is controlled by:reducing power consumption from the electric grid; increasing the powerconsumption from the electric grid; reducing power supplied to theelectric grid; or increasing the power supplied to the electric grid. 3.The method of claim 2, further comprising: modeling, by the controlprocessor, the supply of power realizable by each respective mobiledevice based on operating constraints of the electric grid and of therespective mobile device.
 4. The method of claim 3, wherein in responseto the power output changes from the at least one renewable energysource decreasing: selecting one or ones of the mobile devices that donot have the operating constraints to prevent a reduction of the powerconsumption by the respective mobile device from the electric grid; oran increase of the power supplied by the respective mobile device to theelectric grid; and controlling, by the processor, an adjustment of thepower realized by the selected one or ones of the mobile devices tooffset the decreasing power output from the at least one renewableenergy source.
 5. The method of claim 4, further comprising:determining, for each respective mobile device that is selected, theadjustment of the power realized based on the operating constraints ofthe respective, selected mobile device and the operating constraints ofthe electric grid.
 6. The method of claim 3, wherein in response to thepower output changes from the at least one renewable energy sourceincreasing: selecting one or ones of the mobile devices that do not havethe operating constraints to prevent an increase of the powerconsumption by the respective mobile device from the electric grid; or areduction of the power supplied by the mobile device to the electricgrid; controlling, by the processor, an adjustment of the power realizedby the selected one or ones of the mobile devices to offset theincreasing power output from the at least one renewable energy source;and determining, for each respective mobile device that is selected, theadjustment of the power realized based on the operating constraints ofthe respective, selected mobile device and the operating constraints ofthe electric grid.
 7. The method of claim 1, wherein: the determining,the sending and the adjusting are repeated based on the measured powerfrom the at least one renewable energy source such that aggregate powerrealized by the mobile devices substantially follows generation from theat least one renewable energy source.
 8. The method of claim 1, whereinthe determining of the operating condition for each respective mobiledevice includes selecting, by the processor, a current operatingcondition of the respective mobile device such that at least operatingconstraints of the electric grid and the respective mobile device arenot exceeded.
 9. The method of claim 1, wherein the balancing of thepower realized by the mobile devices with the supply of power from theat least one renewable energy source includes: modeling, by theprocessor, the supply of power realizable by the respective mobiledevice based on operating constraints of the electric grid and theoperating constraints of the respective mobile device, as a modelresult; aggregating, by the processor, the model result for eachrespective mobile device, as an aggregated model result; and comparing,by the processor, the aggregated model result to the measured output todetermine an adjustment of the power realized by each respective mobiledevice.
 10. The method of claim 9, wherein the determining of theoperating condition for the respective mobile device includes selecting,by the processor, a current operating condition of the respective mobiledevice based on operating constraints of the electric grid and each ofthe mobile devices and the comparison of the aggregated model resultwith the measured output of the at least one renewable energy source.11. The method of claim 1, wherein the at least one renewable energysource includes one or more of: a wind generator; a hydroelectricgenerator; a geothermal generator; a wave generator; a currentgenerator; a photovoltaic generator; or a solar thermal generator. 12.The method of claim 1, wherein: the electric grid includes one or moreenergy storage units; and balancing of the power realized by the mobiledevices with the supply of power from the at least one renewable energysource is based on the power output by the renewable source includingpower consumed or supplied by the one or more energy storage units. 13.The method of claim 1, wherein the power realized by the mobile devicesincludes one or more of: the power consumed by the mobile devices; orthe power supplied by the mobile devices.
 14. The method of claim 1,wherein the mobile devices include one or more of: a plug-in electricvehicle; a mobile computing device; a personal digital assistant;portable consumer equipment; a portable power tool; or a game system.15. The method of claim 1, wherein the telemetry information from therenewable resource telemetry device is real-time telemetry information,and the telemetry information from the telemetry devices associated witheach of the mobile devices is real-time telemetry information.
 16. Themethod of claim 1, further comprising: receiving, by an aggregatedtelemetry database, connection event information of a mobile device to agrid connection point; aggregating, by the aggregated telemetrydatabase, the connection information of the mobile device; and sending,by the aggregated telemetry database, the aggregated connectioninformation to the control processor for billing purposes.
 17. A controlprocessor for managing at least one renewable energy source for supplyof power via an electric grid, comprising: the control processorconfigured to: receive one or more selections of service offeringsprovided by the at least one renewable energy source from customersassociated with respective mobile devices; continuously monitor powerfrom the at least one renewable energy source based on telemetryinformation from a renewable resource telemetry device; determineaggregated power realized by the mobile devices based on telemetryinformation received by the control processor from telemetry devicesassociated with each of the mobile devices; send signals to mobiledevices electrically connected to the electric grid to offset poweroutput changes from the at least one renewable energy source with theaggregated power realized by the mobile devices and control currentoperating conditions of the mobile devices so that the aggregate powerrealized by the mobile devices during consumption or supply follows orsubstantially follows the power supplied from the at least one renewableenergy source measured from the renewable resource telemetry device,wherein the current operating conditions include operating points of themobile devices and controlling the operating condition includesadjusting in aggregate the operating points of the mobile devices;receive measurements of the power supplied from the at least onerenewable energy source; and for each respective mobile device used tobalance the power on the electric grid, determine an operating conditionfor the respective mobile device in accordance with the measured powerof the at least one renewable energy source and send the determinedoperating condition to the respective mobile device.
 18. The controlprocessor of claim 17, wherein the control processor signals to themobile devices to adjust the power realized by the mobile devices to:reduce power consumption from the electric grid; increase the powerconsumption from the electric grid; reduce power supply to the electricgrid; or increase the power supplied to the electric grid.
 19. Thecontrol processor of claim 17, wherein the processor is furtherconfigured to: continuously signal the mobile devices such that thepower realized by the mobile devices substantially follows the supply ofthe power from the at least one renewable energy source; and model thesupply of power realizable by each respective mobile device based onoperating constraints of the electric grid and operating constraints ofthe respective mobile device, as model results, aggregates the modelresults for the mobile devices, as an aggregated model result, andcompares the aggregated model result to the monitored power from the atleast one renewable energy source to determine an adjustment of thepower realized by the mobile devices.
 20. A method of managing renewableenergy services for plug in-vehicles, comprising: identifying a fixedaccount that is associated with a grid connection point used by at leastone plug-in electric vehicle for realizing power during a connectionevent; determining, by the at least one plug-in electric vehicle, aquantity of the energy realized during the connection event; adjustingthe identified fixed account based on the energy realized by the atleast one plug-in electric vehicle during the connection event;registering the at least one plug-in electric vehicle and one or moreselections of service offerings provided by a renewable energy sourceselected by a customer associated with the at least one respectiveplug-in electric vehicle, to a renewable energy account; realizingenergy by the at least one plug-in electric vehicle at a plurality ofgrid connection points associated with respectively different fixedaccounts, as a plurality of connection events, in accordance with theregistered customer selections; offsetting power output changes from theselected renewable energy source with the power realized by the at leastone plug-in electric vehicle by controlling, with a control processor, acurrent operating condition of the at least one plug-in electric vehicleso that the power realized by the at least one plug-in electric vehiclemeasured by an associated telemetry device during consumption or supplyfollows or substantially follows the power supplied from the selectedrenewable energy source measured by a renewable resource telemetrydevice, wherein the current operating condition is an operating point ofthe at least one plug-in electric vehicle and controlling the operatingcondition includes adjusting the operating point of the at least oneplug-in electric vehicle; receiving measurements of the power suppliedfrom the renewable energy source; determining an operating condition forthe at least one plug-in electric vehicle in accordance with themeasured power of the renewable energy source and sending the determinedoperating condition to the at least one plug-in electric vehicle;aggregating, by the control processor, the energy realized by theplug-in electric vehicle during the connection events; and billing, therenewable energy account based on the aggregated energy realized.
 21. Amethod of identifying a grid connection point for utility billprocessing of a charging event associated with a renewable energy sourcefor supply of power via an electric grid, comprising: establishing anidentity tag at the grid connection point that uniquely identifies thegrid connection point; receiving, at a mobile charging device, identitytag information to uniquely identify the grid connection point;registering one or more selections of service offerings provided by therenewable energy source from a customer associated with the respectivemobile charging device; monitoring, by the mobile charging device,charge event information indicating attributes of the charging event;offsetting power output changes from the renewable energy source withthe power realized by the mobile charging device by controlling, with acontrol processor, a current operating condition of the mobile chargingdevice so that the power realized by the mobile charging device measuredby an associated telemetry device during consumption or supply followsor substantially follows the power supplied from the renewable energysource measured by a renewable resource telemetry device, wherein thecurrent operating condition is an operating point of the mobile chargingdevice and controlling the operating condition includes adjusting theoperating point of the mobile charging device; receiving measurements ofthe power supplied from the renewable energy source; determining anoperating condition for the mobile charging device in accordance withthe measured power of the renewable energy source and signaling thedetermined operating condition to the mobile charging device;associating, by the mobile charging device, the charge event informationwith the identity tag information, as associated information, inaccordance with the registered customer selections; and sending, by themobile charging device, the associated information for reconciliation ofutility billing accounts associated with the grid connection point andthe mobile charging device.